Breadcrumb bar

[xzxzlala]

Breadcrumb bar of hazel.
Now merged the haz3l-module branch.
could show the current function/module you are in, and the droppings contains other same level functions/modules.
The level is decided by how many funs/modules you are in.
For example, below the cursor is in f1 and g3 and finally in M2:

[disconcision]

how about something like this?

(we should also just stick those icons in the nut menu)

[Negabinary]

Sorry, another annoying little detail!! For pattern matching over expressions like this we like to write out every case, instead of having a catch-all "_ => ..." so that if anyone else adds anything to the language, the compiler will force them to update this function.

[Negabinary]

sure, here's a couple tricks that might help:

1. you can combine patterns when pattern matching
2. you can add a "when" to pattern matches as well

so this whole thing could probably become just one pattern match with four cases

switch (Id.Map.find_opt(List.hd(ancestors_lst), info_map)) {
  | Some(Info.InfoExp({Fun(_), ancestors, _})) when List.length(ancestors) >= 1 => [ ... ]
  | ...

[cyrus-]

how about something like this?

(we should also just stick those icons in the nut menu)

yeah this looks good!

[cyrus-]

@xzxzlala I think we actually want to include let bindings of regular values, not just functions, in the list + we want to show siblings of the current position, even at the top level. we can have a special "dot" location for when you aren't on a binding.

[xzxzlala]

@xzxzlala I think we actually want to include let bindings of regular values, not just functions, in the list + we want to show siblings of the current position, even at the top level. we can have a special "dot" location for when you aren't on a binding.

Sure, I will add the "dot" for cursor not in bindings.
I'm a little bit confused about using let binding of regular values. Won't that lead to lots of levels (fill all the room for top bar)?

[cyrus-]

@xzxzlala I think we actually want to include let bindings of regular values, not just functions, in the list + we want to show siblings of the current position, even at the top level. we can have a special "dot" location for when you aren't on a binding.

Sure, I will add the "dot" for cursor not in bindings. I'm a little bit confused about using let binding of regular values. Won't that lead to lots of levels (fill all the room for top bar)?

It will add more items to the dropdown but it shouldn't increase the horizontal width much since that is based on depth -- it isn't common to nest let bindings very deeply.

[xzxzlala]

@xzxzlala I think we actually want to include let bindings of regular values, not just functions, in the list + we want to show siblings of the current position, even at the top level. we can have a special "dot" location for when you aren't on a binding.

Sure, I will add the "dot" for cursor not in bindings. I'm a little bit confused about using let binding of regular values. Won't that lead to lots of levels (fill all the room for top bar)?

It will add more items to the dropdown but it shouldn't increase the horizontal width much since that is based on depth -- it isn't common to nest let bindings very deeply.

I see, I misunderstand that. We want all other regular values to be siblings in same level and when in the body of new functions/modules we add another level.

[cyrus-]

There would be a new level whenever one binding is nested in another, so also in

let x = 
  let y = 2| in 
  y + 1
in 
x

[disconcision]

k i'm good to restyle if you want. when this is current with dev i'll branch off and do the restyling, then PR against this

[cyrus-]

Seems to be quite buggy right now -- try moving around the following program:

let x = 2 * 3 in 
let y = 3 * 4 in 
let z = 2 * 3 in 
x

It should indicate x only when in the expression 2 * 3 but it indicates z there. Similar issues elsewhere.