4 ms·
> I could see it quickly becoming intractable to find where the code lives that is causing a certain outcome. (Author here.) The tangler I describe inserts #li
by akkartik 7y ago
> I could see it quickly becoming intractable to find where the code lives that is causing a certain outcome.
(Author here.) The tangler I describe inserts #line directives into the output. You can open up the generated C++ and see where a line comes from. Conventional C++ tools understand line directives as well, so the debugger experience is sane.
I'm sure there are gaps in this tooling, but they're not intractable. Tooling around conventional modules has matured over decades. My approach hopefully shows some benefits of a road not taken.
- _bxg1 7y agoIt's certainly interesting, and I didn't mean to pre-judge too strongly. I definitely think we're at the point where we need some new ideas around this stuff, and probably any new ideas at this point will require some kind of special editor assistance, so yeah, I get what you mean in that regard.