Clash doesn’t pick the name of the function being specialized

[martijnbastiaan]

Christiaan described this as:

It doesn’t pick the name of the function being specialized when it has a NOINLINE, while the argument being specialized on does not

over at #2502 (comment). I'm actually unsure why we would ever pick solely the argument's name instead of the function's name.

[martijnbastiaan]

I've proposed a patch that does the, IMO, more sensible thing:

Given a global binder accum and an application mealy accum, Clash now calls the new, specialized binder mealy_accum instead of just accum. This more accurately reflects the body of the function and will result in more sensible file names. For example, previously Clash would generate a separate file accum.{v,vhdl} that contained the inlined bodies of both mealy and accum. AFter this patch, it will generate mealy_accum.{v,vhdl}.