Deprecate map.field() syntax suggestion

[hst337]

@zachallaun

I also generally disagree that it’s misleading

module.function(1, 2, 3) # Is a call
module.function(1) # Is also a call
module.function() # Is a call and also a map lookup

This is the “misleading” I am talking about

---

@zachallaun

Isn’t this just a constraint of parsing/syntax? In your example, it’s not possible to know whether map.x() is a key lookup on a map, or a function call on a module, until runtime

It is impossible to know for sure, but compiler is already able to check the types and warn when map.field() is called when map is a map. Plus, runtime warning is okay too.

---

@josevalim

We have been planning on adding a runtime deprecation for a while and there is an open issue tracking this.

Great! I am sorry, I didn’t check the issue tracker