Hi. That would help in packaging for fedora to have a license file include in the crate.

On windows the \ isn't escaped so you end up with oninput="send('src\main.rs::VALUE', Number(this.value), 'f64')", which is an invalid path because the backslash escapes the m.

padraig_oh on reddit suggested to create a list of generated constant values that can be copied. I would like to add this to the web GUI as a textbox where you can copy the changed values.

The comment above this line is inaccurate as to what it is doing, and the usage of transmute here to create a reference with longer lifetime is not sound.

The transmute itself does not cause a leak of the value. It is purely a pointer cast, and has no semantic effect on the machine state. What this is doing is the opposite, it is asserting to the compiler that your code has done something to the effect of leaking the value, but that the compiler just can't see. That, however, is wrong.

Also note that creating a statically shared reference to the value is not what you want as that would disallow any mutable reference being created for the whole remaining program lifetime. Creating any mutable reference is UB as long as a shared reference exists, thus it would be allowed for the compiler to optimize out any of the writes done by the web server. More likely though, it will instead deduplicate some reads of the referred-to value which could cause writes to appear to have no effect.

Uriopass on reddit suggested this. Organizing/grouping the widgets per module would make the interface a lot better.

Constants are only added when they are accessed, this is a problem now because constants that are accessed in a later stage are not displayed in the web GUI.