-
-
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
String constructor can segfault #16470
Comments
Cf. discussion following #16107 (comment). I also think methods playing with pointers should all be marked |
I don't really have a strong opinion here so whenever you guys decide what we should call this, I'll change it. If this is going to go out of the |
(If we rename Maybe just |
We could also have a more generic API, which would allow extensions for custom string types. Something like |
…unsafe_string_wrapper, and unsafe_array_wrapper; restore non-copying behavior of String(::Vector{UInt8}) constructor (closes JuliaLang#16470, closes JuliaLang#16713)
…unsafe_string_wrapper, and unsafe_array_wrapper; restore non-copying behavior of String(::Vector{UInt8}) constructor (closes JuliaLang#16470, closes JuliaLang#16713)
…unsafe_string_wrapper, and unsafe_array_wrapper; restore non-copying behavior of String(::Vector{UInt8}) constructor (closes JuliaLang#16470, closes JuliaLang#16713)
expected result:
MethodError
,"Ptr{UInt8}(1)"
, anything but crashing?Julia constructors shouldn't segfault, only methods that can should have
unsafe_
in the nameThe text was updated successfully, but these errors were encountered: