-
Notifications
You must be signed in to change notification settings - Fork 729
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
Support accessing relevant member functions on a wider variety of types #4435
Labels
enhancement
New feature or request
Milestone
Comments
I like this quite a bit because it reduces nesting and is much easier to write and reason about: // contrived example with method syntax
myString.toUpper().toLower().length()
// current syntax
length(toLower(toUpper(myString))) |
+1, I like this too. We'll need to think about what the behavior around completions and validations should look like for the |
Should behave like C# extension methods |
I discovered this feature has a name! UFCS: https://en.wikipedia.org/wiki/Uniform_Function_Call_Syntax |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The example from the discussion below is for
string
types, but could be expanded for more:Discussed in #4429
Originally posted by CShen-RACI September 13, 2021
Just my 2 cents, do you guys think it will be better to use program language way to call the function? For example to convert string to upper case, which way is better
upper(rgName)
or
rgName.Upper()
The text was updated successfully, but these errors were encountered: