Robert Muir
Robert Muir
I will play with the "don't reformat javadoc option". Maybe it's an easier solution to these problems? If we can coerce Google formatter to treat `///` as javadoc then problem...
@dweiss I'm wondering if we could send them a PR such that any `///` line comment respects the `--skip-javadoc-formatting` flag (or some other flag to say "dont mess around"). it...
@dweiss I think that is because google-java-format uses internal JDK compiler apis to parse it. just like error prone. it is why you have to add all the opens?
@dweiss very nice. the `///` can have leading whitespace in front of it which is preserved too. I dont know how their parser works but you can simulate the leading-case...
awesome! I really hope the patch is accepted: this will definitely give us a path forward.
yeah: only thing I will say about choice of formatter is that normally I try to configure the editor in the repo to match what the build expects. e.g. for...
I think your description is correct. There are size implications with some of these dictionaries as well, they can be enormous.
> Yes, it was a Graviton3 (`m7g`) CPU. `lscpu` says: from the cpu's [optimization guide](https://developer.arm.com/documentation/109897/latest/):
Just as a general comment around this performance: the 256-bit SVE vectors available on these processors have unfortunately not had a lot of love from our side. Lots of digging...
afaik 16-bit fp support is in newer versions of java (21?) and being worked on for vector api there too. not sure of its current state.