Re:GitHub Codespaces
by hannibalhorn on Wednesday May 06, 2020 @08:43PM
(#23098329)
That'd be awesome!
math.Pow10() already uses arrays this way, and I found a ~10% performance while optimizing an alternative float parsing implementation by making the same change.
[ Parent
| on HN ]
Re:GitHub Codespaces
by toomuchtodo on Wednesday May 06, 2020 @08:52PM
(#23098382)
I just want to say kudos and well done to post the diff here.
Re:GitHub Codespaces
by tom_mellior on Thursday May 07, 2020 @09:16AM
(#23102599)
Didn't you just poison this change and ensure that it can never be applied? Having posted this anonymously, nobody can sign the Contributor License Agreement and promise truthfully that this is original code that they have the rights to contribute. Including yourself, in the future.
You can not copyright the ... (dot dot dot) nor can you claim copyright to an existing work by adding ... to it. You might be able to pattern it though...
Re:GitHub Codespaces
by tom_mellior on Friday May 08, 2020 @01:41AM
(#23111734)
I don't know the specifics of Google's contributor agreement (you need to log in with a Google account just to read it), but in my experience they are much stricter than copyright law. I've heard of organizations that would like to force people to sign contributor agreements just to be allowed to open GitHub issues. Because the issue might contain information that might taint everything. At least in the view of corporate lawyers.