From: Jean Privat Date: Tue, 3 May 2016 01:26:26 +0000 (-0400) Subject: Merge: Qualified Class Names X-Git-Url: http://nitlanguage.org Merge: Qualified Class Names After #2034 and #2041 , some of you might had some theories about future episodes. While this is not GoT, I hope the you found that the following is a nice surprise: qualified class names are now understood by the tools. The specification is the following: On conflicting class-names, you can use the package_name to qualify the class. i.e. `package_name::ClassName`. This is enough for all public class, since it is the canonical name for them. For conflicting private classes, the package_name should be enough in most cases. If there is still a conflict, you need to precise also the name of the module. i.e. `package_name::module_name::ClassName`. Qualified properties is a more complex thing, and since the class is used as a namespace for them, there is statically less property name conflicts (except for classes commonly refined, like Sys maybe). So I plan to put qualified properly names in a boat heading to King’s Landing and let them row. Pull-Request: #2047 Reviewed-by: Alexis Laferrière Reviewed-by: Romain Chanoir --- 3fe5fcf063e51ef7528886e52cc63832760fc89c