Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Undefined behavior
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Examples in Rust == While undefined behavior is never present in safe [[Rust (programming language)|Rust]], it is possible to invoke undefined behavior in unsafe Rust in many ways.<ref>{{cite web | title=Behavior considered undefined | website=The Rust Reference | url=https://doc.rust-lang.org/reference/behavior-considered-undefined.html | access-date=2022-11-28}}</ref> For example, creating an invalid reference (a reference which does not refer to a valid value) invokes immediate undefined behavior: <syntaxhighlight lang="rust"> fn main() { // The following line invokes immediate undefined behaviour. let _null_reference: &i32 = unsafe { std::mem::zeroed() }; } </syntaxhighlight> It is not necessary to use the reference; undefined behavior is invoked merely from the creation of such a reference.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)