3 ms·
It is the implementation which matters, or rather, the observable consequences of the implementation, which in effect form part of the interface of the abstract
by twic 11y ago
It is the implementation which matters, or rather, the observable consequences of the implementation, which in effect form part of the interface of the abstraction - they might not be intended, but they're there. Those are what we call leaks.
The abstraction i was thinking of was byte arrays, which are provided by the language, rather than anything higher-level. Many languages have byte arrays which guarantee that you can't read past the end, and can't read values that you didn't write. Java would be one example.