Hi all,
I wanted to clarify, and discuss if needed, our styling of #define guards. My
understanding is that we are now using Google's style in regards to #define
guards (https://google.github.io/styleguide/cppguide.html#The__define_Guard). I
believe this would mean for `dom/media/foo/bar.h` I w
On Wednesday, July 3, 2019 at 2:27:30 PM UTC-7, Chris Peterson wrote:
> On 7/3/2019 11:37 AM, Bryce Seager van Dyk wrote:
> > I wanted to clarify, and discuss if needed, our styling of #define guards.
> > My understanding is that we are now using Google's style in regards to
On Sunday, July 21, 2019 at 10:18:02 PM UTC-7, Karl Tomlinson wrote:
> Near the top of
> https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style
> there is
> > New code should try to conform to these standards, so it is as
> > easy to maintain as existing code. [...]
> >
> > T
On Monday, August 12, 2019 at 8:41:26 AM UTC-7, Emilio Cobos Álvarez wrote:
> If you don't use mozilla::Result, then you can stop reading now.
>
> Result always returned the ok / errors by value. That's fine when the ok
> or error values are cheap / small, like integers, but over time we've
> be
Thanks both for the clarifications.
There is a use case that I'd like to clarify the performance + sanity of. I
hope discussion here will be useful to others looking to use Result, but please
let me know if it's more suitable to take elsewhere.
In the Media stack I often want to return a Resu
5 matches
Mail list logo
