Skip to content

chore: Explicit deprecate attributes - #5

Open
krlmlr wants to merge 12 commits into
f-deprecate-explicitfrom
claude/f-deprecate-explicit-42ve6t
Open

chore: Explicit deprecate attributes#5
krlmlr wants to merge 12 commits into
f-deprecate-explicitfrom
claude/f-deprecate-explicit-42ve6t

Conversation

@krlmlr

@krlmlr krlmlr commented Aug 17, 2026

Copy link
Copy Markdown
Owner

Patch f-deprecate-explicit of the stack.

cpp11::sexp's implicit conversions to double, size_t and bool are marked "DEPRECATED: Do not use this, it will be removed soon." in a comment, which nothing enforces. Adding [[deprecated(...)]] makes the compiler say so at the call site, which is where the reader needs it — these are implicit conversions, so the call site does not mention them at all.

Each attribute carries the message naming the conversion, so a warning identifies which of the three fired.

The declarations are reflowed by clang-format, which is why the diff is larger than three attributes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01K8MneV8KqHYUuC8fWV3X5Q


Generated by Claude Code

DavisVaughan and others added 12 commits April 3, 2026 13:09
* Don't rely on transitive include of `"fmt/core.h"`

We got it through `cpp11/protect.hpp`, but we should not rely on that

* Correctly use `fmt::runtime()` on runtime strings passed to `fmt::format()`

In fmt, there is a `FMT_CONSTEVAL` macro that resolves to `consteval` on "new enough" C++ (otherwise it doesn't do anything). For R 4.6+, the default C++ used is finally "new enough" (`__cplusplus > 201703L`).

This causes all `fmt::format()` calls to require a constant expression for `const char*` and `std::string&` input, which we are not currently doing via `fmt_arg`.

We have a runtime provided string, which must now be wrapped in `fmt::runtime()`, which is what we should have been doing all along.

* Add `r_ns_env()` and use in `get_namespace()`

Throwing an informative (and tested!) error when we can't find the package namespace

* Define `RCPP_NO_R_HEADERS_CHECK` before all `#include <Rcpp.h>` usage

`#include <cpp11/R.hpp>` sets everything up the right way, and otherwise we get a warning from Rcpp which doesn't seem to end up being relevant for this use case

* Use `r_env_has()` + `r_env_get()`

To avoid triggering a NOTE about usage of `Rf_findVarInFrame3()` on R 4.5, where technically we had the tools to avoid that
* Teach `cpp_source()` how to source multiple files

* NEWS bullet

* Link to PR
…violations (r-lib#493)

* Add failing test

* Use tag types to generate attribute specific internals

* NEWS bullet

* Formatting
* Update `cran-comments.md`

* Increment version number to 0.5.5
@krlmlr
krlmlr changed the base branch from main to claude/main-42ve6t August 17, 2026 21:12
@krlmlr
krlmlr changed the base branch from claude/main-42ve6t to f-deprecate-explicit August 17, 2026 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants