| |
 | Posted by user1234 in reply to Monkyyy | Permalink Reply |
|
user1234 
Posted in reply to Monkyyy
| On Wednesday, 7 May 2025 at 14:49:21 UTC, Monkyyy wrote:
> On Wednesday, 7 May 2025 at 13:32:41 UTC, user1234 wrote:
> On Monday, 5 May 2025 at 22:52:57 UTC, monkyyy wrote:
> As we all should know, the ast is modified live and the compiler never deallocates. This leads to compiler bugs that give glimpses behind the veil. Such bugs features I think are actually quite valuable when the devs are overly cautious, see them disallowing ct io.
Whats the current knowledge of compiler bugs, and how to use them? Anyone found any that Im unaware of?
mmmh, do you want to know if people are secretly using undocumented compiler bugs like a secret magic knowledge ? That would not be reliable. Someone else can notice the problem, report it, later it gets fixed, and then your exploit does not work anymore.
Sorry if I'm "off the spot" but in first place your question was not very clear.
I think several of the bugs I found will never be fixed, probably can't be except by completely disallowing the syntax or major rewrites of systems(the live editing of the ast, is a feature, probably why d is fast while c++ is slow) and there is an compiler fork.
The "live editing of the ast" works (I assume you talk about mixin) because the front-end decomposes analysis in several phases. There are well observed limits however. Not always specified.
|