Hide unhygenic tokens generated by macros from symbol search

[jkelleyrtp]

Due to lifetime issues, our macros need to generate a variety of intermediary structs/statics. These show up in symbol search, which clutters up the search significantly. These are technically unhygenic.

I would be happy to fix this with a little bit of guidance.

In this screenshot, I can't actually find the Template struct I'm looking for since the list is filled with the intermediate TEMPLATE object we make in the macro.

It's not just dioxus macros, it's every macro. This is for tracing:

[Veykril]

These are technically unhygenic.

They aren't though, they are spanned with call_site meaning they are exposed. def_site would be required to hide these (which a) is obviously still unstable so not an option and b) not honored by this by r-a yet, not that it matters).

So we can't really just hide these away as we'd then actually hide away other constructs that are properly exposed by macros. As for the tracing case we could maybe special case _ prefixes for symbol search and have those be hidden as an escape hatch for def site hygiene being not a thing yet.

[jkelleyrtp]

I'd be happy to add a filter for _ or __ - would we want to hide the symbol completely or allow them to show up if there's a specific search for _?

I've already changed our macros to spit out __TEMPLATE - I think that'd be easy for the ecosystem to lightly standardize on.

[Veykril]

or allow them to show up if there's a specific search for _

Would probably be nice to allow that, though I don't know if VSCode will allow us to do that. It is overly strict with the symbol search on the client side in what is allowed to be done and what not unfortunately.

I'd say let's require two underscores then, I imagine some people use a single one for reasons so that's special enough for people to specifically opt-in here until we get def site hygiene.