W3C home > Mailing lists > Public > public-fxtf-archive@w3.org > April 2018

Re: [fxtf-drafts] [geometry] Why does DOMQuad have readonly mutable points?

From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
Date: Wed, 25 Apr 2018 21:33:06 +0000
To: public-fxtf-archive@w3.org
Message-ID: <issue_comment.created-384441314-1524691985-sysbot+gh@w3.org>

Yep. In general overloading, especially for constructors, is not something we want to spread.

-- 
GitHub Notification of comment by domenic
Please view or discuss this issue at https://github.com/w3c/fxtf-drafts/issues/124#issuecomment-384441314 using your GitHub account

Received on Wednesday, 25 April 2018 21:33:14 UTC

This message: [ Message body ]
Next message: Dirk Schulze via GitHub: "Re: [fxtf-drafts] [geometry] Why does DOMQuad have readonly mutable points?"
Previous message: Simon Pieters via GitHub: "Re: [fxtf-drafts] [geometry] Why does DOMQuad have readonly mutable points?"
Maybe in reply to: Dirk Schulze via GitHub: "Re: [fxtf-drafts] [geometry] Why does DOMQuad have readonly mutable points?"
Next in thread: Dirk Schulze via GitHub: "Re: [fxtf-drafts] [geometry] Why does DOMQuad have readonly mutable points?"

Mail actions: [ respond to this message ] [ mail a new topic ]
Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]
Help: [ How to use the archives ] [ Search in the archives ]

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:22 UTC