4 ms·
Ergonomic wise what holds Julia back other than the deployment story is that they refuse to adopt nims universal call syntax approach f(a,b) = a.f(b)
by singularity2001 3y ago
Ergonomic wise what holds Julia back other than the deployment story is that they refuse to adopt nims universal call syntax approach f(a,b) = a.f(b)
- geysersam 3y agoWhy is that better?
- singularity2001 3y agoFamiliarity and more importantly discoverability: If you type a. in the REPL or IDE you should get a list of all functions applicable to the object
- deleted 3y ago[deleted]
- Mikhail_K 3y agoJulia is not an OO language, and its functions dispatch on all function arguments, not just the first one.
- geysersam 3y agoFamiliarity changes rapidly in the world of software development. But I do agree about discoverability. However, I think the issue is rather that we need to find new discoverability systems that work for multiple dispatch rather than limit our languages to single dispatch because we can't come up with better ways to achieve discoverability. Maybe (a,b)f would be better syntax.. or we could start writing backwards ;) but now we're getting into seriously unfamiliar territory. Multiple dispatch might actually be superior for discoverability when we get this right because you can filter the method list based on all arguments rather than just the first one.
- teleforce 3y agoI'm pretty sure Nim copied that from D language. As they always said, imitation is the sincerest form of flattery.
- xgdgsc 3y agoYou can use my fork of vscode julia extension for this https://github.com/xgdgsc/julia-vscode/releases/tag/v1.41.1_methodswith https://github.com/xgdgsc/julia-vscode/releases/tag/v1.41.1_...
- Shorel 3y agoDo you mean D-lang universal call syntax approach?