Allow using "get", "set" and "delete" as method/property names about adobe-runtime-support HOT 2 OPEN

Just to clarify what you mean, you would like to be able to have something like:

public class Map
{
    public function set(key:*, value:*) : void
    {
        // stuff
    }
}

I think the compiler might be challenged to differentiate that from:

public class Map
{
    public function set myval(key:*, value:*) : void
    {
        // stuff
    }
}

which is a property setter..

Is there any reason you couldn't use capitalised versions or something to differentiate it from the reserved words? I'd be a little hesitant about changing those kinds of things..

thanks

from adobe-runtime-support.

Yes, that's exactly what I mean. I'm also want to use some other reserved keywords like break, continue, default...
The reason is, in some case I think they're the best names to use.
In above example, I just want my classes (Map/Set) to have same API compared to JavaScript, so anyone that familiar with javascript can use my lib right away.
Set.delete()
Map.delete()
Map.get()
Map.set()

Another example, I have a class AsyncLoop that can construct something like for loop. It can handle multiple items need to be loaded/processed asynchronously. And I need some functions called break, continue to break/continue the async loops.

I'm also building some library that use command line processes. The command line APIs have flags/switches named include, default... And I want to use them as property names.

In some programing languages, there're ways to use reserved names. For example in C# I can use the @ prefix.

Back to your example, I think it's quite easy to distinguish:

public class Map
{
    public function set(key:*, value:*) : void
    {
        // if there's nothing after set, so set is the function name
    }
}
public class Map
{
    public function set myval(key:*, value:*) : void
    {
        // there's something after set (myval), so set is a keyword
    }
}

from adobe-runtime-support.