Tuesday 15 April 2014

language design - Pros and cons of Go rejecting unused dependencies -


Google's new language tries to simplify dependency management. The compiler will reject a module that announces dependency on a module without using any of that module.

This package is illegal for importing or importing packages for themselves, the exporter's identifier.

I can think of some obvious benefits (such as a cleaner module), but maybe there is some non-obvious only one loss which I can think is an excessive PDC compiler, There is a lot of complaints during refactoring, but maybe more?

Do you have any experience with other languages? What are the pros and cons of this approach?

Not only do you need to explicitly use all dependencies, but also use all the variables needed. The compiler will give you errors when you have unused variables.

They are upset but will make others happy because they get clean codes.

I think that probably want designers to go, become a language which is largely dependent on IDE.


No comments:

Post a Comment