panic! must be a form, not a function #7

New Issue

scott · 2023-12-14T01:30:17Z

kredati commented

2023-12-14 01:30:17 +00:00

(Migrated from github.com)

To get better information, panic! should be a language-level form, not a plain-old function. This will allow it to capture the line information for where a panic is explicitly initiated.

To get better information, `panic!` should be a language-level form, not a plain-old function. This will allow it to capture the line information for where a panic is explicitly initiated.

kredati commented

2023-12-15 02:18:15 +00:00

(Migrated from github.com)

panic! is scanned as a keyword
panic! gets parsed as panic! {non-binding}
panic! is wired up to the interpreter along with a line number

- [x] `panic!` is scanned as a keyword - [x] `panic!` gets parsed as `panic! {non-binding}` - [x] `panic!` is wired up to the interpreter along with a line number

scott self-assigned this 2023-12-15 21:25:22 +00:00

scott commented

2023-12-18 05:27:14 +00:00

Resolved by #15

scott closed this issue

2023-12-18 05:27:24 +00:00

scott reopened this issue

2023-12-18 05:27:39 +00:00

scott removed the

now

label 2023-12-18 05:27:52 +00:00

scott closed this issue