nselvara

I also see the error and I'm using the latest version of VHDL-LS. The workaround that you've provided is cool though, didn't know that. I don't know if that's feasible:...

> Yea, something like that is definitely possible and will be implemented at some point. Note, however, that the example I gave is very simple. In a more general case,...

Sorry, I didn't mean in particular the linter but the static code analysis. As an example this one could serve: https://github.com/VHDL-LS/rust_hdl/issues/184 Or this one: https://github.com/VHDL-LS/rust_hdl/issues/191

I see, yeah I mean for the mean time that would be a sufficient solution. It's more like for developers who work on those projects could be a hint that...

Hihi, yes the shorter one is more preferable to analyse. 😸

Or maybe, we introduce 2 kind of flags, which then indicates that the object is only used as a reference and the other one remains the same if it's not...

I found another one that's related to this: This one flags that the index is not used. ```vhdl variable bla: boolean; function ret_bla(index: natural) return boolean is begin return true;...

I think making a generic type package would solve the problem.

Currently, the checker checks for a condition that occurs when the data rate is variable which is set by stimuli. As the stimuli has some arbitrarily long wait time it...

Well, the data rate itself is kind of changing as it's a random number that I generate for each iteration. I also thought about defining the key at a global...