wow this thread murdered my notifications today. I super appreciate all the feedback, folks!!
-
-
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
significantly de-prioritize parsing, focus on defining a simple IR and focus on analysis (type analysis, CFGs, etc.) and transformations. (I'm biased - IMHO, all of the interesting action occurs between the parser and back-end code emitter).
-
I totally agree but there's this conflicting fact that parsing is the most important thing for most people to learn, since parsers are everywhere and bad parsers are responsible for like 70% of security problems
- Još 6 drugih odgovora
Novi razgovor -
-
-
The modern query-based architecture for compilers (the pull-model) in addition to just the regular pipeline architecture (the push model) There's a great video about this from a couple of years ago that introduced me to the difference:https://channel9.msdn.com/Blogs/Seth-Juarez/Anders-Hejlsberg-on-Modern-Compiler-Construction …
-
woah, have never seen this, thanks
- Još 2 druga odgovora
Novi razgovor -
-
-
https://chocopy.org - Recently revamped Berkeley's compiler class using ChocoPy. A favorite tool was the web IDE -- students' own parsers/type-checkers can power the highlighted error messages, and they can step-through their generated RISC-V in the web browser as well.
-
wow, awesome!
- Još 2 druga odgovora
Novi razgovor -
-
-
Some content around compiler correctness (esp covering material related to compcert and/or Chlipala's FRAP book) and static analysis could really set a course apart! Though honestly that could be a whole course on its own, and fitting it in at an undergrad level seems challenging
-
I absolutely want to get into correctness, and I absolutely do not want to try to get undergrads to use proof assistants. SMT solvers are the way to go!
- Još 2 druga odgovora
Novi razgovor -
-
-
At least 6-8 weeks of lexing and parsing
-
for real?
- Još 3 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.