Jacques Carette
Jacques Carette
So, I shouldn't merge this until that's done?
So one way to handle "dependent choices" is to have the data-structures direct them. Let me take `Architecture` as the example (even though it might go away); `Unbundled` would stay...
Having constraints as a separate thing that explicitly lists the variables that it depends on is an excellent idea. Then we could do a topological sort and output things in...
Indeed, the high-level APIs have suffered from too much ad hoc evolution. I think this is because "lists" are rendered in all sorts of different ways in different languages. For...
Why did you change Bundled to Unbundled in one example? Also, if you could rebase, so that it's easier to see what's new in just this PR?
`drasil-codegen` is probably best, at least for our current level of understanding.
Could you be more precise about what code in `LanguagePolymorphic` is not used by Julia? [I mostly want to be more informed, I don't have any conclusions in any direction...
> I checked the CodeInfoProc.hs and CodeInfoOO.hs and found some common instances: [...] In a subsequent PR, yes, that likely makes sense.
Amusingly, for all but `inlineIf` and `while`, everything that's called C-like and re-used by Julia could have been called "functional" too! Maybe some of that stuff deserves to be made...
Serves me right for approving before the build finished... And I've just done it again.