1
ysc3839 2019-09-17 20:21:16 +08:00
装了 MSVC 之后会带上这些代码的,我认为这次“开源”的意义在于授权协议以及接受开源社区的贡献。
|
2
by73 2019-09-17 23:02:42 +08:00
你不是都贴了链接嘛:
> Q: Why are you doing this? > > A: There are several reasons. Working on the STL in GitHub will allow our customers to follow our development as it happens, try out our latest changes, and help improve our pull requests by reviewing them. As C++ Standardization accelerates, with more large features being voted in every year, we believe that accepting major features as open source contributions will be important. (For example, C++20’s chrono and format libraries are potential candidates.) We also want to contribute back to the C++ community by making it possible to take our implementations of major features. (For example, C++17’s charconv.) 简而言之就是微软想摸鱼了(雾),想让大家提交 pull requests。 |
3
zhuangzhuang1988 2019-09-17 23:25:36 +08:00
给华为施加压力?
|
4
kuroismith 2019-09-17 23:44:28 +08:00
@zhuangzhuang1988 stl 作为模板库的代码本来就是公开的...
|
5
kqz901002 2019-09-17 23:48:21 +08:00
@kuroismith #4 公开!=开源
|
6
66450146 2019-09-17 23:59:53 +08:00
@kuroismith 虽然源代码都能看到,但是 MSVC 的许可证不允许。如果在其他地方使用这套代码的话是侵犯 MSVC 的许可,这事就可大可小了,上规模的公司都会远离的,甚至禁止员工阅读。现在许可证允许了这些行为就可以光明正大阅读和提交修改了,当然也要在许可证允许的范围内
用 LLVM Apache 2.0 也是很重要的一部分,基本上排除了其他公司商业应用的障碍 |
7
Mithril 2019-09-18 08:05:31 +08:00
估计是觉得 C++标准每年新出的东西太多实在做不完了,几个 STL 库大家互相帮助一下算了。
新出的功能一家做一个,互相一抄就全有了。 开源以后 License 都改成一样的就完全没问题了。 |
8
wangkai0351 2019-09-18 09:53:37 +08:00
@Mithril STL 没区别,剩下全靠编译器优化??这比的多累啊
|