Re: Should we split the project into two branches?

[H. Nikolaus Schaller]

> Am 15.02.2022 um 08:44 schrieb Max Chan <xcvista@me.com>:
> 
> This is just whack…
> 
> What I mean by saying we need refactoring, is that our library structure is 
> twisted and may not bode well for future Swift integration. Here is ours:
> 
> * libc
>  * libobjc2
>    * Foundation (NSObject here)
>      * CoreFoundation
> 
> And here is Apple’s:
> 
> * libc
>  * libobjc2 (NSObject here)
>    * CoreFoundation
>      * Foundation
>      * Swift Standard Library
> 
> Now do you see my point? (Don’t worry with Swift Standard Library to 
> Foundation toll-free bridging, all of those goes through CoreFoundation.)

We had a long discussion about that when CoreFoundation API came. At that time 
there was no Swift.
So it felt the easiest thing to add the new API by wrapping existing Foundation 
classes...

But what I wonder is the following:
If Foundation and CoreFoundation have well defined and stable interfaces why 
does implementation matter at all?
Is there even a requirement that they are layered on each other?
Can't they be completely separate implementations of some API used by compilers 
and developers?