| 02:36 | <jmdyck> | Anthony Bullard: The GNU project's coding standard for C recommends a space before the open-paren in a function call: https://www.gnu.org/prep/standards/standards.html#index-spaces-before-open_002dparen |
| 02:37 | <Anthony Bullard> | Anthony Bullard: The GNU project's coding standard for C recommends a space before the open-paren in a function call: https://www.gnu.org/prep/standards/standards.html#index-spaces-before-open_002dparen |
| 02:42 | <jmdyck> | My impression is that Allman style deals with indentation and brace-placement, not space-before-left-paren: https://en.wikipedia.org/wiki/Indentation_style#Allman_style |
| 15:21 | <Timo Tijhof> | It seems various ES specs have problems with their table of contents (there's an uncaught JS error in the console, using latest Firefox). At least ES8.0 and ES7.0 both don't seem to be able to expand sections in the TOC, and can't search either. https://262.ecma-international.org/8.0/ |
| 15:21 | <Timo Tijhof> | Are these generated by something under TC39 on GitHub? |
| 17:56 | <bakkot> | Timo Tijhof: Looks like some of the asset links got broken. Those ones are handled by ECMA, not github; the ones on github are fine: https://tc39.es/ecma262/2017/ |
| 17:57 | <bakkot> | cc littledan ljharb I don't know what the best way to report issues to ecma's webmaster is, but the stylesheets and scripts in https://262.ecma-international.org/8.0/ currently have the wrong sources |
| 18:01 | <ljharb> | i think I’ve reported that one before :-/ i usually just email Patrick and cc samina. Feel free to do so and cc me, or else i can do it later today |
| 20:15 | <littledan> | Aki: ? |
| 20:24 | <Aki> | Y’all report like you normally world and I’ll look into it on my end. (I have zero access to all that but maybe I could) |