balicat commented on PR #285:
URL: https://github.com/apache/arrow-dotnet/pull/285#issuecomment-4896858816

   Chased it down: dotnet/roslyn#70701. Under the original C# 12 rules a char 
collection expression was deliberately treated as *convertible* to `string` for 
overload-resolution purposes (LDM 2023-10-02) — even though actually 
constructing the string errors — so `Split(['='], 2, …)` was ambiguous by 
design against the `(string, int, StringSplitOptions)` overload that exists on 
netstandard2.1. The collection-expression betterness revisions in C# 13-era 
compilers resolve it in favor of `char[]`. Since the repo sets `LangVersion` 
latest and has no global.json, the behavior tracks whichever SDK does the 
build: my 8.0.128 still carries the old rules, while CI and presumably your 
machine run something newer. Updating my local SDK.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to