Hiroaki Yutani

I don't know well about these positional aesthetics, but it sounds fine to me.

@buggaby Thanks, but it seems your data is not suitable for `geom_raster()`, which expects > `geom_raster()` is a high performance special case for when all the tiles are the same...

The error comes from here: https://github.com/tidyverse/ggplot2/blob/9eae13b3d17bde26cf9df649887b4a6bb2ac92ce/R/geom-raster.r#L72-L79 I found the very small jitterings in data cause `NA`. ``` r data_error [11] 0.000000e+00 -1.110223e-16 -2.220446e-16 -3.330669e-16 -4.440892e-16 #> [16] 4.440892e-16 3.330669e-16 3.330669e-16...

It saves us from the errors, but the some part of the raster will get lost then... We should not shave the raster, but lower the resolution instead. For example:...

Thanks. When I reviewed the pull request, I didn't consider the semantics of `*just` carefully. I'm not sure I'm for or against the suggestion at the moment, but, at least,...

I think we can consider this now. R 4.3 should be only about half a year away.

I don't remember well, but, in my case, the workaround was to remove `` or to add `__mingw_ldbl_type_t` to the blocklist.

I like `create()`, but I'm afraid it sounds too magical. In my understanding, the function is rather for experts compared to `mutate()` and `summarize()` with single-row-returns, so probably it should...

[Rustonomicon](https://doc.rust-lang.org/nomicon/send-and-sync.html) says: > raw pointers are neither Send nor Sync (because they have no safety guards).

I might be wrong, but, in my understanding, pointers are not Sync or Send simply because there's no mechanism to prevent data race or access conflict. For example, it's possible...