adding whole-project loading

[Saizan]

Updates hls to hie-bios 0.20 and takes advantage of its new LoadMode to add "whole project" components loading: loads all components specified in the cradle from the start, regardless of which files are open.

TODO:

• Updated docs in doc/configuration.md
• Add tests

[Saizan]

@fendor let me know if you have a better field name than componentsLoading

[Kleidukos]

We should definitely not deprecate sessionLoading without warning first. :) Happy to make sure that the next HLS announcement on the Haskell blog includes it.

[fendor]

Can we open an issue proposing what the changes to HLS are?

[fendor]

Changes look good to me, primarily a question of UX and naming

[Saizan]

Created issue #5005 to document design

[Kleidukos]

Good work so far @Saizan, I'm seeing a couple of things that I'd like you to clarify:

1. There seems to be both needed-only and only-needed, is that desired? We should probably stick with multi: needed-only.

2. You seem to have introduced the double usage of multipleComponents (full words, plural) and multiComponent (abbreviated, singular). Please stay with multipleComponents:

              [ show @String old_value ++ " (deprecated)"
        ==>   | old_value <- ["singleComponent","multiComponent"]
              ]

3. I feel like there is a similar disparity between "session loading" and "component loading" but maybe I'm wrong?

[Saizan]

@Kleidukos thanks for catching that, decided to give a name to these strings, see last commit.

[Kleidukos]

@Saizan Do you know if we can expect an increase in memory consumption when enabling this feature? Would you mind sharing memory profiles before / after your patch? Not a blocker but this could certainly bring light on stuff we could work on afterwards. :)

[Saizan]

@Kleidukos you mean compared to multi: needed-only but when we actually need the whole project, or something else?

Or would you like to know how much memory extra "unneeded" components amount to?

I would assume it's going to be fairly dependent on their composition, do you have a project in mind we could take as a benchmark? Otherwise I suppose the natural choice is HLS itself.

[Kleidukos]

@Saizan Starting with HLS itself is not a bad choice at all! Basically what I'm interested in is what the average end-user can expect in terms of resource consumption after upgrading, with a project that has multiple packages.

Or would you like to know how much memory extra "unneeded" components amount to?

Something like this, yes. Basically if you have a workflow of "navigating a codebase with multiple components / packages in a project, what does that change for the end-user in terms of reactivity and does that blow up their memory usage". :)