We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jotting down some notes from discussion with @gamburgm
RacketScript runtime throws exceptions in different ways right now:
racketscript/racketscript-compiler/racketscript/compiler/runtime/core/struct.js
Line 173 in c1f802a
check.js
racketscript/racketscript-compiler/racketscript/compiler/runtime/core/check.js
Line 2 in 71fdbaa
error.js
racketscript/racketscript-compiler/racketscript/compiler/runtime/kernel.rkt
Line 401 in 71fdbaa
racketscript/racketscript-compiler/racketscript/compiler/runtime/core/marks.js
Line 118 in 71fdbaa
Ideally, RS would have one unified api for errors, and use it consistently everywhere.
One complicating factor is that different parts of Racket itself doesnt respect abstractions sometimes:
error
raise-arguments-error
raise <exn struct>
So any solution would need to be handle both scenarios above
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Jotting down some notes from discussion with @gamburgm
RacketScript runtime throws exceptions in different ways right now:
racketscript/racketscript-compiler/racketscript/compiler/runtime/core/struct.js
Line 173 in c1f802a
check.js
(kernel fns) also directly raises JS (e.g., TypeError) exceptionsracketscript/racketscript-compiler/racketscript/compiler/runtime/core/check.js
Line 2 in 71fdbaa
error.js
apiracketscript/racketscript-compiler/racketscript/compiler/runtime/kernel.rkt
Line 401 in 71fdbaa
racketscript/racketscript-compiler/racketscript/compiler/runtime/core/marks.js
Line 118 in 71fdbaa
Ideally, RS would have one unified api for errors, and use it consistently everywhere.
One complicating factor is that different parts of Racket itself doesnt respect abstractions sometimes:
error
orraise-arguments-error
raise <exn struct>
So any solution would need to be handle both scenarios above
The text was updated successfully, but these errors were encountered: