Skip to content
New issue

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

A more precise description of no-…-description conditions #8

Open
38a938c2 opened this issue Apr 6, 2019 · 0 comments
Open

A more precise description of no-…-description conditions #8

38a938c2 opened this issue Apr 6, 2019 · 0 comments

Comments

@38a938c2
Copy link

38a938c2 commented Apr 6, 2019

Right now implementation says that a name being not present in a lexical environment is a program-error (which seems a bit off, as variable-description is probably the recommended way of checking if a variable exists in an environment, and program-error is expected to be used for syntax-level errors). At the same time, specification neither says that the return value is nil in case the variable doesn't exist, nor that the condition signalled is a serious condition. This could lead to divergence between implementation-specific Trucler protocol support libraries.

Personally, I think returning NIL after signalling a non-serious condition would make the most sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant