On 9/20/2018 5:17 PM, Julian Foad wrote:
A fresh perspective on the experimental-APIs issue just came to me: this should
not hold up the 1.11 release. We were falling into the old trap of thrashing
about debating how to do it, assuming we needed some solution for 1.11, but we
don't. One of the rules of time-based releases: something that need not block
it should not block it.
We should just pull the experimental APIs from the public API space (moving
them into the private API space) and get on with the release.
But if they're in the private space, other clients can not use them.
Sure, I could add some workaround in the TSVN build to pull in the
private headers, but then that would mean I wouldn't get any compiler
error if I actually use a private and not just an experimental API.
Why not just leave it like it is for now - the docs clearly mark the
APIs as experimental, and IMHO that's good enough (at least for now).
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
