Some have suggested using the following syntax to keep class access within packages package com.foo While there is some truth to this, many developers moving from Java to Kotlin are still used to using Package organization engineering, and package-level access will help achieve better code isolation, so many still want to add related capabilities. Kotlin's team believes that packages used to be units of components, but now that modules are a more common component granularity, access should be designed around modules, so package-level access is not designed. Internal makes the entire Module visible. Package-level access control permissions are provided in Java, but Kotlin lacks the corresponding access control character. Kotlin encourages developers to use top-level methods instead of Util classes, but when there are too many such top-level methods, we expect a similar namespace mechanism.Ī common workaround today is to use the Object class instead of static methods, for example object DisplayUtil Copy the code Package-private Visibility

Java can call a Class's static method or variable by Class name, which implicitly provides a namespace mechanism for quickly indexing a constant or method. If you like these features, you can go to YouTrack and upvote them. In line with the 2022 Technology Trends essay campaign, which focuses on fleece plucking, here's a bold prediction of what Kotlin might introduce in the future via YouTrack's most popular current issues: People can submit their ideas and issues to the community through YouTrack, and some of the popular issues will be managed and maintained by Kotlin team, and may be finally implemented and appear in a future version. Kotlin is an open language, not just open source, and any user can directly participate in its construction. 'What will be hot and what to learn in 2022? This article is participating in the' Talk about 2022 Technology Trends 'essay campaign.

Kotlin mapof