Skip to content
This repository has been archived by the owner on May 16, 2019. It is now read-only.

Leaking top level #56

Open
AndreasVolkmann opened this issue Feb 7, 2019 · 0 comments
Open

Leaking top level #56

AndreasVolkmann opened this issue Feb 7, 2019 · 0 comments

Comments

@AndreasVolkmann
Copy link

AndreasVolkmann commented Feb 7, 2019

There are a number of variables and functions that are declared at top level and leak through since they are not marked as internal.

An example could be the val OPERANDS = ... in RequestPreProcessing.kt. There are many more.

This pollutes the global scope.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant