-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
unexpectedly broad tuple type in Optim.hz_linesearch! #6097
Comments
Note you can also comment out that final argument entirely, and simply set |
Unfortunately I was not able to replicate this with a simple test like
|
What I see so far is that the type of |
the general problem was that one place in the code had a larger type for a tuple than another. I don't know why, but we can at least generate correct code instead of crashing. there was already some code in boxed() towards handling this kind of thing, but it needed to be rearranged a bit.
The crash is fixed. There is just some wonky sub-optimal type inference which might be a bug, not sure. |
That is odd. Thanks for fixing the crash! I'll let you be the one to decide when to close this. |
It's not clear to me that the crash is fixed, because now it is crashing PyCall... see my comment at 764098f. |
@stevengj it works for me on master now. |
Yup, no crash for me any more. |
Using the
master
branch of Optim, and modifying the default value of this line to0x23
results in a reliable segfault when runningtest/runtests.jl
.The text was updated successfully, but these errors were encountered: