-
Notifications
You must be signed in to change notification settings - Fork 1
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
New version of Chapel cripples Chrest #8
Comments
Here is
and
|
I will try to reproduce the error. |
Reproduced on my machine
|
Seems to be fixed, will have @Tshimanga confirm when he can. |
Yep, all clear! @buddha314 @marcoscleison |
What was the fix? |
I'm not sure, but I think he had to add |
Just to clarify, I think these failures were a result of this PR that adds throwing errors to string casts: When I mentioned "error checking" offline I meant semantic errors related to initializers like use-before-def errors with fields. |
Hi all, I have some Reflexion module usage. Inside the reflection, I use type cast. the compiler was crying because the code block that uses type casts was not with try{}. I added try{} and silenced the compiler for while. |
@marcoscleison et al: More information on error handling approaches can be found here, which should help you avoid fighting the compiler in the future. |
@benharsh updated chapel to be much more strict in error checking. My experience has been that putting a
try!
in front gets past the error, but may not be the best solution.The text was updated successfully, but these errors were encountered: