Hadley Wickham

I have a vague recollection it was something to do with scale customisation. Maybe so that you could write your `scale_colour_continuous()` to override the defaults?

@bersbersbers this only works by coincidence and not by design. We make no guarantees about the ggplot2 internals and making it possible replaying saved plots from previous versions of ggplot2...

@lionel- can you take a look at this when you start integrating the new rlang error stuff into dplyr?

I assume you discussed and rejected adding another variable to the existing `name` specification? i.e. `across(x:y, quantiles, .names = "{outer}.{inner}.{fn}")`? Or do we assume that when unpacking there's only ever...

Hmmmm I like the way this looks, but adding the extra attribute is makes a lot of tests fail. I'm confident we can work around this for dplyr itself (see...

@cderv nope, nothing specific that I can recall.

I think we can probably change this, but someone will need to carefully explore which `tbl` subclasses currently rely on `fortify.tbl` and figure out what methods will be needed to...

Thanks for filing this issue! Unfortunately, I think it's currently out of scope: developing good software requires relentless focus, which means that we have to say no to many good...

See discussion in #6281

This breaks: * bigrquery * childesr * ckanr * dm * etl * farr * funneljoin * geospark * RPresto The fixes are generally straightforward (import `dbplyr::sql()` instead of `dplyr::sql()`)...