Closed XiaoPangxie732 closed 1 month ago
The analyzer test failure is unrelated, and due to a change in string.is_upper() that happened in https://github.com/vlang/v/pull/21358 , while v-analyzer's CI was not ran after that (we only test that v-analyzer itself builds on the main V CI, and not that v-analyzer's CI passes).
I am not sure whether to fix pascal_case_to_snake_case or its tests, but I am more inclined to change pascal_case_to_snake_case
to preserve its old behavior. @ttytm what do you think?
- if c.ascii_str().is_upper() {
+ if c.ascii_str().is_upper() || c.is_digit() {
Would make it pass with the current utils tests. Additionally including a check of the last letter would make it more safe.
- if c.ascii_str().is_upper() { + if c.ascii_str().is_upper() || c.is_digit() {
Applied in 2584e86 .
(rebased over current main
)
v install
should not be concerned with compilation flags. And the actual compiler is determined bybuild.vsh
:Also, the executable has
.exe
extension on Windows, thusv-analyzer.exe
should be copied on Windows