bassislife

8 ms·

1. 31.▲
   by bassislife 11y ago

   > which LLVM now supports Key word being "now". I think you understood rather well. Also have a look at the supported architectures paragraph in the documents you linked.
2. 32.▲
   by bassislife 11y ago

   > Writing to LLVM in no way restricts you to a backend. You simply need a language-level IR that you can retarget to different backends as you would like. It still ignores toolchain flexibility. Especially given the specific needs of Go&
3. 33.▲
   by bassislife 11y ago

   Compile times ? Flexibility over the backend ? That would be my hunch. I think it makes a lot of sense. Also, note that there is that project which exists : http://llvm.org/viewvc/llvm-project/llgo/
4. 34.▲
   by bassislife 11y ago

   Alas, to his defense, it's slightly unnerving to read malinformed, biased critics all-thread long. I would really advise him to try and ignore most of them if he wants to keep his sanity though. (serious, been there, done that.) Especi
5. 35.▲
   by bassislife 11y ago

   Well, the purpose of types is to enable design by contract among other things. Therefore, I am also a bit dubious about IFC. It seems to me that Data Flow Analysis is more suitable. We are essentially hinting at the same thing I guess, but