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

Defsetf Lambda-Lists Don't Permit the &environment Parameter #129

Open
Shinmera opened this issue May 22, 2018 · 0 comments
Open

Defsetf Lambda-Lists Don't Permit the &environment Parameter #129

Shinmera opened this issue May 22, 2018 · 0 comments
Labels

Comments

@Shinmera
Copy link

Shinmera commented May 22, 2018

This is in violation to 3.4.7 which specifically allows the &environment parameter in defsetf lambda-lists.

Test case:

(defsetf foo (&environment env place) (value))
;; => Bad lambda list  (&ENVIRONMENT ENV PLACE).

I'm not entirely sure if 3.4.7 requires &environment to come after the places, unlike other lambda-lists where &environment can be anywhere. In any case, late &environment also fails in the same fashion.

(defsetf foo (place &environment env) (value))
;; => Bad lambda list  (PLACE &ENVIRONMENT ENV).

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

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

No branches or pull requests

2 participants