Hacker News new | ask | show | jobs
by kzrdude 1706 days ago
It must be clearly understood which of the flags are entirely safe and which need to be under 'unsafe', as a prerequisite.

Blanket flags for the whole program do not fit very well with Rust, while point use of these flags is inconvenient or needs new syntax.. but there are discussions about these topics.

1 comments

Also maybe you woild like to have more granular control over which parts of your program has the priority on speed and which part favours accuracy. Maybe this could be done with a seperate type (e.g. ff64) or a decorator (which would be useful if you want to enable this for someone elses library).
Maybe... or maybe there would be just a flag to enable all this and be fine with consequences.
..have you used Rust?

> just a flag to enable all this and be fine with consequences

Is probably the opposite of what the language is about.

Reasoning about the consequences along a couple functions in your hot path is one thing. Reasoning about the consequences in your entire codebase and all libraries is quite another.