Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only switch to absl::string_view implementation on Windows. #2307

Merged

Conversation

hzeller
Copy link
Collaborator

@hzeller hzeller commented Dec 23, 2024

On gcc and clang-based systems, std::string_view has the iterator behave as expected by a lot of Verible code, being a const char*.

On windows c++ lib, the iterator is its own object, which does not decay to const char*, so in that case we need to use the absl:: implementation which behaves like that.

We used to always change to the absl type, but in reality, we only need to do that on Windows; adapt the abseil patch.

Longer term, we should remove the expectation of the iterator type, but that requires access to a Windows machine to locally go through a compile/fix loop.

On gcc and clang-based systems, std::string_view has the iterator
behave as expected by a lot of Verible code, being a const char*.

On windows c++ lib, the iterator is its own object, which does
not decay to const char*, so in that case we need to use the absl::
implementation which behaves like that.

We used to always change to the absl type, but in reality, we only
need to do that on Windows; adapt the abseil patch.

Longer term, we should remove the expectation of the iterator type,
but that requires access to a Windows machine to locally go through
a compile/fix loop.
@hzeller hzeller merged commit e7d381d into chipsalliance:master Dec 23, 2024
29 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant