Loading RoCreators…
Transfer practice · Repair the syntax and return subtotal after a discount. A missing end and a misspelled returned local are separate issues.
v3 · Activity 1 of 1 · errors · tracing · 10 min Runs here
Use a familiar idea in a different task. Read the changed requirement before running.
Repair the syntax and return subtotal after a discount. A missing end and a misspelled returned local are separate issues.
Interface: questLabel(quest:{name:string,done:number}) -> string
| Input | Expected |
|---|---|
Discount10, 3 | 7 |
Large discount3, 10 | 0 |
local function label(item)
print(type(item.quantity))
return item.name .. ": " .. tostring(item.quantity)
end
return labelThe trace tells you the quantity type before formatting. It helps diagnose a field mismatch without rewriting the whole function.
New syntax: runtime error line numbers
A syntax error means the compiler could not read the program. A runtime error means the program started but an operation could not work with the values it received.
An error line identifies a useful place to inspect, not necessarily the only cause. Trace the input and each local used by that expression.
print can reveal intermediate values during Run code. Avoid putting private data in output when asking for help. Keep the failed code draft so you can compare it with the repair.
Select a word or symbol in this authored example. Your editor draft stays unchanged.
labelitem
item.quantity
item.name item.quantity
labelThis is a private experiment copy. It does not replace your answer or complete the activity.
These inputs apply when your scratchpad returns the function described by the activity interface.
Your output will appear here.
Replace this code with the starter? Download your draft to keep a copy.
Your output will appear here.
Sign in with RoCreators to save private progress across devices. Community verification is separate.