Viktor Kojouharov
Viktor Kojouharov
Hi, The generated code doesn't really use reflection. Do you have an example of where using a comparable constraint would help improve things?
The problem is that currently you can write something like this ```go var foo = map[string]struct{ Foo int }{ "1": {Foo: 1}, "2": {Foo: 2}, } ``` which is why...
Not sure if that's better or not. You'd have 2 different syntaxes for the same thing now. In some places, both can be used, but in others, only 1 can...
In terms of cognitive overhead, i really don't see how adding an extra `_` is that much better, tbh. Lets take the following examples: ```go foo := Config{ Bar: {...
Just for disambiguation, wouldn't it be better to use `_{}` for maps/slices as opposed to structs, since they are less likely to occur in the wild, while keeping structs representations...
Perhaps, rather than allowing a const struct to be assigned to a superset struct, only allow assignment to a comparable one. For supersets, we could propose _yet another usage of...
Hi, Unfortunately, the frontend is in react. It looks like most of the work for faceted search will go into the frontend, so that will complicate things. I would be...
interesting. what's the angular-cli version you are trying to build with? it looks like whatever the `ng` command is in the container, it doesn't recognize these flags. also, probably not...
It looks like a good solution. No idea how hard implementing that would be
Sure, go for it