Thomas Schwinge

@jcrowgey: Thanks for looking into this, and no worries about the delay. I also haven't really been proactive with *ping*ing this. Thanks for your review; that all makes sense, and...

Does my #282 "CreateEventFromVOBJ: if there is no dtend, use the duration if available" help?

Ha, @davidmalcolm -- now you beat me to that one, great! I had seen your GCC master branch commit 0b14f590e3e9d95b8211b77d992589d5ab4c25f0 "diagnostics: add ability to associate diagnostics with rules from coding...

@bjorn3: Hrm, that URL does work for me. I do get a 404 if accessing via _HTTPS_; but this is plain _HTTP_ (unless your browser is doing something funny maybe?)....

@philberty, I don't know much yet about the structuring of the GCC/Rust front end, but yes, a "layered approach" does seem to make sense. For example, don't attempt semantic analysis...

I think I know where/how to conceptually do such a thing in GCC; will provide details at some later point in time.

Nice! Generic GCC abstractions for the win -- "it just works"! :-) Unless anybody gets there first, I shall turn this into a GCC/Rust test case.

ACK. In context of thinking about re-using the `rustc` error codes (that was even before @davidmalcolm's #1408 "Experiment: add optional error codes to diagnostics"), I also had this thought: whether...

I'm lacking all context here, but if this is feasible then I'm all in favor, instead of copying GCC/C++ code, adapting it for GCC/Rust, and then having effort/difficulties picking up...

This issue came up again in context of "[14 regression] GCC fails to bootstrap with 'rust-tree.cc:131:10: error: ‘NON_DEPENDENT_EXPR’ was not declared in this scope'", where in "rust: build failure after...