zentol commented on pull request #17133: URL: https://github.com/apache/flink/pull/17133#issuecomment-929064318
> Would it make sense to enforce that all **public** classes are required to have a visibility annotation I'm not sure. On the one hand it forces the dev to make a decision w.r.t. visibility, which is good, but at the same time I could imagine this being very annoying overhead. Because of that I'm worried that we'd just end up slapping `@PublicEvolving` on everything and calling it a day (which de-facto already happens in the APIs). And then I'm wondering what the real benefit actually is. Actually, I would not enforce that for now, because we should rethink `@Experimental/@PublicEvolving` anyway. As is we enforce _nothing_, so really, what's the point. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
