Add lint against ptr-to-int transmutes in consts

[RalfJung]

We do not allow ptr-to-int casts in const context, so people might be tempted to do a transmute instead. This will not work, and if they ever actually test their code during CTFE they will get an error, but it might still be good to add an extra layer of defense here (since this is a rather odd corner of the language) and have a lint for this.

@jhpratt started working on this, here's a link.

[RalfJung]

Cc @rust-lang/wg-const-eval

@jhpratt do you want to work on this, or leave this issue open for anyone to pick up?

[jhpratt]

Someone else can pick this up, as I've got other priorities for the near future. As I mentioned feel free to use the code linked.

It's worth noting that a lint would ideally also catch transmutes that use a union, though that would be quite a bit more difficult I imagine.

[RalfJung]

It's worth noting that a lint would ideally also catch transmutes that use a union, though that would be quite a bit more difficult I imagine.

That'll require a lot of complexity, for a case that I assume will be exceedingly rare. So I don't think that is effort, lines of code, and compile time well spent.

[jhpratt]

Agreed. Just throwing it out there.

[oli-obk]

More context on the lint can be found in the discussion starting at #85769 (comment)

[clubby789]

@rustbot label +A-const-eval

[veera-sivarajan]

@rustbot claim