Skip to content
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

typeof() in the type language #3228

Closed
bblum opened this Issue Aug 20, 2012 · 5 comments

Comments

Projects
None yet
5 participants
@bblum
Copy link
Contributor

bblum commented Aug 20, 2012

I'm not sure if this would be useful in every-day code, but I just wrote some code where it would've been nice to say:

let foo: typeof(earlier_thing) = unsafe::transmute(...);

instead of

let foo: complicated::typename::that_might_change_later = unsafe::transmute(...);
@sanxiyn

This comment has been minimized.

Copy link
Member

sanxiyn commented May 3, 2013

Nominating for backwards compatible milestone.

@graydon

This comment has been minimized.

Copy link
Contributor

graydon commented Jun 20, 2013

reserving the keyword at least is required for this to be backwards-compatible; actual feature is later

@graydon

This comment has been minimized.

Copy link
Contributor

graydon commented Jun 20, 2013

accepted for backwards-compatible milestone

@cmr

This comment has been minimized.

Copy link
Member

cmr commented Aug 5, 2013

This would be very nice.

@thestinger

This comment has been minimized.

Copy link
Contributor

thestinger commented May 10, 2014

This is the kind of thing we really need to go through the new formal RFC process. There's never going to be enough discussion here. It's no longer a backwards compatibility issue because typeof is reserved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.