-
Notifications
You must be signed in to change notification settings - Fork 65
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
interpreter: broken constructors when ending with a return
#2546
Labels
Comments
xymus
added a commit
to xymus/nit
that referenced
this issue
Aug 31, 2017
Signed-off-by: Alexis Laferrière <alexis.laf@xymus.net>
xymus
added a commit
to xymus/nit
that referenced
this issue
Aug 31, 2017
Signed-off-by: Alexis Laferrière <alexis.laf@xymus.net>
privat
added a commit
to privat/mynit
that referenced
this issue
Dec 20, 2017
fixes nitlang#2546 Signed-off-by: Jean Privat <jean@pryen.org>
privat
added a commit
to privat/mynit
that referenced
this issue
Dec 20, 2017
fixes nitlang#2546 Signed-off-by: Jean Privat <jean@pryen.org>
Delja
pushed a commit
to Delja/nit
that referenced
this issue
May 17, 2018
Signed-off-by: Alexis Laferrière <alexis.laf@xymus.net>
Delja
pushed a commit
to Delja/nit
that referenced
this issue
May 17, 2018
fixes nitlang#2546 Signed-off-by: Jean Privat <jean@pryen.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the interpreter, constructors ending with a
return
create objects of the wrong type. I've got aBool
and anASCIIFlatString
depending on the context, adding a print inside the constructor caused it to return an emptyASCIIFlatString
.Minimal example:
The text was updated successfully, but these errors were encountered: