You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to explore un-exporting those, but that's a pretty involved project when trying to be considerate of potential breaking changes.
For now, I'd just like to keep the set of exports consistent as I move to {roxygen2}.
The way I'd like to go about that is to put all of these exports that didn't "naturally" wind up with their own @export tag elsewhere in the code base in a single @export tag in bit64-package.R, which I can easily tag with a TODO/bug.
This line would have almost 3,000 characters, though, so I'd like to wrap it. Prepending @export to every line wastes characters and causes visual noise.
AFAIK other tags don't have this restriction so I was surprised to encounter this only with @export.
The text was updated successfully, but these errors were encountered:
I would like to write a truly massive
@export
directive.{bit64} exports a lot of functions, including every S3 method:
https://github.com/r-lib/bit64/blob/f30bae1787f65e0b4bff9c0dbe2addea5ba58877/NAMESPACE
I would like to explore un-exporting those, but that's a pretty involved project when trying to be considerate of potential breaking changes.
For now, I'd just like to keep the set of exports consistent as I move to {roxygen2}.
The way I'd like to go about that is to put all of these exports that didn't "naturally" wind up with their own
@export
tag elsewhere in the code base in a single@export
tag in bit64-package.R, which I can easily tag with a TODO/bug.This line would have almost 3,000 characters, though, so I'd like to wrap it. Prepending
@export
to every line wastes characters and causes visual noise.AFAIK other tags don't have this restriction so I was surprised to encounter this only with
@export
.The text was updated successfully, but these errors were encountered: