Fix invalid std::vector<const std::string> types#11
Open
Conversation
47a4d6a to
5d82b50
Compare
swansontec
approved these changes
Feb 17, 2026
Contributor
swansontec
left a comment
There was a problem hiding this comment.
I approve, but why!?!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Low Risk
Type-only signature corrections across native bindings with no behavioral changes expected beyond fixing compilation on newer toolchains.
Overview
Fixes an invalid C++ type by removing
constfromstd::vectorelement types across the iOS bridge (ZanoModule.mm), Android JNI bridge (jni.cpp), and thezanoMethodswrapper API (zano-methods.hpp/.cpp).Adds an Unreleased changelog entry noting the build fix for Xcode 26.
Written by Cursor Bugbot for commit 5d82b50. This will update automatically on new commits. Configure here.