Skip to content

Conversation

@vogella
Copy link
Contributor

@vogella vogella commented Jun 20, 2025

Nicer to use for end user and API compliant. If this change is integrated we must update the usage of this method in platform to avoid compiler warnings.

@akurtakov
Copy link
Member

As it's semantically coupled with setFilterNames it would be good if they use the same style.

@github-actions
Copy link
Contributor

github-actions bot commented Jun 20, 2025

Test Results

  118 files  ±0    118 suites  ±0   14m 52s ⏱️ +18s
4 647 tests ±0  4 629 ✅ ±0  18 💤 ±0  0 ❌ ±0 
  330 runs  ±0    326 ✅ ±0   4 💤 ±0  0 ❌ ±0 

Results for commit ea961fd. ± Comparison against base commit 67642bd.

♻️ This comment has been updated with latest results.

@vogella
Copy link
Contributor Author

vogella commented Jun 20, 2025

As it's semantically coupled with setFilterNames it would be good if they use the same style.

Will do, I just wanted to see what the general feedback was before doing to much changes.

@akurtakov
Copy link
Member

It's a fine change IMO.

@vogella vogella force-pushed the varargs-usage branch 3 times, most recently from 86f1841 to 20d2103 Compare July 3, 2025 07:54
@akurtakov
Copy link
Member

Would you please fix the 2 new compiler warnings?

Nicer to use for end user and API compliant.

If this change is
integrated we must update the usage of this method in platform to avoid
compiler warnings.
@akurtakov
Copy link
Member

To be finished with github.com//pull/2700

@akurtakov akurtakov closed this Oct 29, 2025
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.

2 participants