|
|
|
|
|
|
by MeetingsBrowser
16 days ago
|
|
|
The blog post does want to share some type information with users. They just want to prevent users from relying on a specific implementation of that type. They are basically describing a public API backed by a private type that they can extend, rearrange, or otherwise modify without breaking the public contract. |
|
|