You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ideal fix for this would be to make NSObjects not Sized; then the example code wouldn't even compile. Unfortunately, it doesn't seem that there's a way to make a struct not Sized without the struct using "fat" (two-word) references, which would be incorrect for an NSObject.
Activity
SSheldon commentedon Jan 17, 2015
The ideal fix for this would be to make NSObjects not
Sized; then the example code wouldn't even compile. Unfortunately, it doesn't seem that there's a way to make a struct notSizedwithout the struct using "fat" (two-word) references, which would be incorrect for an NSObject.SSheldon commentedon Jan 31, 2015
If rust-lang/rfcs#709 were accepted, this could be resolved by marking NSObjects as
NotSized.SSheldon commentedon Feb 11, 2015
The unsized types RFC was postponed as rust-lang/rfcs#813.
[-]mem::swap doesn't work with NSObjects[/-][+]mem::swap doesn't work with Objects[/+]SSheldon commentedon Apr 22, 2017
If rust-lang/rfcs#1861 is accepted, we could fix this by making Object an opaque extern type.
SSheldon commentedon Dec 6, 2017
The extern types RFC was accepted and implemented! Stabilization tracked in rust-lang/rust#43467.
nox commentedon Dec 11, 2017
Getting mutable references to void types is undefined behaviour to begin with, will file an issue.
Merge pull request SSheldon#6 from madsmtm/no-std-exception