You're right on both counts. The mechanism of implementation will be very close .. which is what is in the proposal too. Having programmed in Erlang, I feel th

You're right on both counts. The mechanism of implementation will be very close .. which is what is in the proposal too. Having programmed in Erlang, I feel that the notation (i.e. syntax) influences moment to moment thinking. So if there is overlapping notation between method invocation and message passing, I expect increased opportunity to code and design incorrectly, resulting in subtle bugs. Making "async message passing" syntactically explicit and obivous clarifies a lot and prevents expectations of calling other methods, facing compiler errors, or worse having to deal with specified behaviours that may not be what I had in mind. Edit: one example of this confusion in the spec is the whole part about inheritance in actors ... which looks like a terrible idea to me.