Peter Lebbing

You could argue that I'm going off-topic with this post, since most of it is not about ILA's or VIO's. However, you are suggesting we stop using `setName` because of...

Ah perhaps this is what irks you? I managed to at least foul up the names of the ILAs a bit. Normalisation introduced `` ticks, I think because it duplicated...

Right now, I'm thinking that once a user uses `setName`, that should override the prefix. The name will still be made unique by Clash, but if the user picks a...

Yes, that is a good thing, but maybe not for `setName`! That's my thinking. [edit] You snuck in an edit after I replied :-). My full reply is below. [/edit]

Maybe if the user comes at the point where they cannot tell apart their `setName X` from their `setName X` elsewhere, that is the point where they should refine their...

I also think it is confusing that sometimes the prefix is not there, i.e., when Clash didn't have to inline any definitions. Compare `f` and `g` in [this comment](https://github.com/clash-lang/clash-compiler/issues/2655#issuecomment-1925272120). `g`...

Wow, yeah, that use case is nasty. I generated HDL for that code, and in my case, the first ila was called `ila_1`, the second `ila_0` and the third `ila`.

Note to self: TODO: - [ ] Combine with PR #2672

Note to self: TODO: - [ ] Combine with PR #2672

@kloonbot run_ci a86a4ec