3 ms·
At a quick glance it looks like it's targeted towards mutable data structures. Can it support (and would it make sense to support) immutable data? E.g. it would
by Zalastax 8y ago
At a quick glance it looks like it's targeted towards mutable data structures. Can it support (and would it make sense to support) immutable data? E.g. it would be nice to have a Haskell state monad that also visualizes its state.
- westoncb 8y agoYou are correct, it's very much targeted toward mutable data structures. It'd be interested in looking more into the state monad and considering the possibilities, but I haven't yet. Actually part of how I see the role of systems like this is part of the necessary conditions for more safely working with mutable data. I think mutable data is more risky, but also super easy to work with, so if we had ways of making it more reliable we should explore them. I envision languages where this sort of visualization is a core feature designed in tandem with the runtime etc.
- Zalastax 8y agoNeat! Very interesting ideas! The Vacuum package[1] seems like something you could look into if you want to explore Haskell. Good luck with your project! [1]: https://hackage.haskell.org/package/vacuum https://hackage.haskell.org/package/vacuum
- westoncb 8y agoThanks! Looks pretty cool. I also found this: http://felsin9.de/nnis/ghc-vis/ http://felsin9.de/nnis/ghc-vis/