Justwerk compiler flag

monkyyy crazymonkyyy at gmail.com
Sun Jul 20 00:39:14 UTC 2025


On Saturday, 19 July 2025 at 20:58:39 UTC, Luna wrote:
> 
> If you know the string is in rw memory; just 
> `(cast(char[])myString)`, no?
>
> Enforcing types invariance is a good thing,
>
> Sometimes things are private for a reason; ...
> As for safe; it exists to prevent code from doing stupid things 
> that should be relegated to low level libraries that have no 
> choice.
>
> your bank details or whatever.
>

Its all function coloring and if theres 5 layers of meta 
programming thats using a string. The same case for, nogc std and 
safe by default can also be made for "strng=char[]" I either 
adopt a lib writers opinions, or I rewrite it from scratch.


---

Other people fundamentally believe more keyword spam is good 
style. I can name a few places in phoboes where my usecase was 
blocked by "contact oriented programming" or a random 
private,*that if I had a reason way to go delete it, my usecase 
would just work*

When in wasm, one of phoboes io functions's contract imported 
something that brought in all of phoboes(and I wasnt at the time 
implementing a real wasm runtime), the copy and pasted function 
just worked

Sumtype get!(int) is the exact api I would suggest for extending 
sumtypes to work with ranges, its private

sort asserts on you using a probabilistic comparison

etc. etc. etc.

Safety is just one of many color of functions, theres plenty of 
historical president for coloring functions to be more safe like 
the dip's


More information about the dip.ideas mailing list