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.

Copy link
Contributor

github-actions bot commented Jun 20, 2025

Test Results

   545 files  ±0     545 suites  ±0   30m 33s ⏱️ +33s
 4 405 tests ±0   4 387 ✅ ±0   18 💤 ±0  0 ❌ ±0 
16 741 runs  ±0  16 599 ✅ ±0  142 💤 ±0  0 ❌ ±0 

Results for commit 20d2103. ± Comparison against base commit 51fed8e.

♻️ 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 2 times, most recently from 16c39d9 to 86f1841 Compare June 26, 2025 08:42
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

Would you please fix the 2 new compiler warnings?

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