Tim
I think this should wait until schema is part of "effect", as it seems like an api that should be owned by the Config module.
Brands (as well as a lot of other things in effect) work with `unique symbol`'s, so if you have two versions of Effect they are going to be completely different....
Thanks for taking the time to look at this :) Replacing `void` with `unknown` does feel weird, feels like we are losing some semantics by making the return types too...
Mainly you lose some meaning / intent. This function returns nothing (void) vs this function could return anything but we don't care what (unknown).
But in terms of familiarity for the majority of developers, most of them know that ```ts const myFn = () => { // No explicit return } ``` Will infer...
Hi, yes we had a discussion on the Discord server before making the change. It simplified a few things, and made the pattern matching more resilient, so we decided to...
Sounds like the opposite of #132 Will likely need feature detection to work around it.
There wasn't really a need to switch, as unique identifiers are already made for all of the services.
The discord-bot project that uses this library is more application level code. I used Context.Tag there. https://github.com/Effect-TS/discord-bot
Maybe instead of enforcing capitalisation, we just reserve the `is` and `match` keywords? If a user wants lower case tags, then I don't think we should prevent that.