Martin Henz

Source Typed gives: display(1, 2); Line 1: TypeError: display expects the second argument to be a string The typechecker passes: display(); // runtime error and display(1, "asdf", 3); // no...

I think we should add a runtime error if display and error have more than two arguments. There is already a runtime error for 0 arguments.

This bug is still there. It was rediscovered by a CS1101S student today.

This issue persists as of today.

I think our syntax highlighting should reflect the focus on specific sublanguages, such as Source §1. Learners with prior knowledge are able to see quickly whether the feature they are...

Yes, error() and display() give runtime error, but passing more than two arguments leads to silently ignoring the extra arguments. Should be an easy fix.

Yes, this looks like the correct specification for this feature.

obsolete: > What happens if we want to display the actual value `undefined`? A small hack would be needed: ``` display(value, "the value is:" + (is_undefined(value) ? " undefined" :...

> Is this a duplicate of #1476? No, it's in addition to #1476. I've clarified the title of this issue.

@Ziwen510 can you take a look at the merge conflicts? It would probably not take much of your time to fix these so that the review can proceed. Tx.