Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
  guess_tspec.Rd: abort
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
File ‘tibblify/libs/tibblify.so’:
  Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘ENCLOS’, ‘EXTPTR_PROT’,
    ‘EXTPTR_TAG’, ‘FORMALS’, ‘FRAME’, ‘HASHTAB’, ‘OBJECT’, ‘PRENV’,
    ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’,
    ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’,
    ‘SET_GROWABLE_BIT’, ‘SET_OBJECT’, ‘SET_TRUELENGTH’, ‘STRING_PTR’
These entry points may be removed soon:
‘EXTPTR_PROT’, ‘EXTPTR_TAG’, ‘FRAME’, ‘HASHTAB’, ‘BODY’, ‘FORMALS’, ‘CLOENV’, ‘ENCLOS’, ‘OBJECT’, ‘SET_FORMALS’, ‘SET_BODY’, ‘SET_CLOENV’, ‘STRING_PTR’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
  guess_tspec.Rd: abort
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
File ‘tibblify/libs/tibblify.so’:
  Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘ENCLOS’, ‘EXTPTR_PROT’,
    ‘EXTPTR_TAG’, ‘FORMALS’, ‘FRAME’, ‘HASHTAB’, ‘OBJECT’, ‘PRENV’,
    ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’,
    ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’,
    ‘SET_GROWABLE_BIT’, ‘SET_OBJECT’, ‘SET_TRUELENGTH’, ‘STRING_PTR’
These entry points may be removed soon:
‘EXTPTR_PROT’, ‘EXTPTR_TAG’, ‘FRAME’, ‘HASHTAB’, ‘BODY’, ‘FORMALS’, ‘CLOENV’, ‘ENCLOS’, ‘OBJECT’, ‘SET_FORMALS’, ‘SET_BODY’, ‘SET_CLOENV’, ‘STRING_PTR’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Namespace in Imports field not imported from: ‘lifecycle’
  All declared Imports should be used.
File ‘tibblify/libs/tibblify.so’:
  Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘ENCLOS’, ‘EXTPTR_PROT’,
    ‘EXTPTR_TAG’, ‘FORMALS’, ‘FRAME’, ‘HASHTAB’, ‘OBJECT’, ‘PRENV’,
    ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’,
    ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’,
    ‘SET_GROWABLE_BIT’, ‘SET_OBJECT’, ‘SET_TRUELENGTH’, ‘STRING_PTR’
These entry points may be removed soon:
‘EXTPTR_PROT’, ‘EXTPTR_TAG’, ‘FRAME’, ‘HASHTAB’, ‘BODY’, ‘FORMALS’, ‘CLOENV’, ‘ENCLOS’, ‘OBJECT’, ‘SET_FORMALS’, ‘SET_BODY’, ‘SET_CLOENV’, ‘STRING_PTR’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Namespace in Imports field not imported from: ‘lifecycle’
  All declared Imports should be used.
File ‘tibblify/libs/tibblify.so’:
  Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘ENCLOS’, ‘EXTPTR_PROT’,
    ‘EXTPTR_TAG’, ‘FORMALS’, ‘FRAME’, ‘HASHTAB’, ‘OBJECT’, ‘PRENV’,
    ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’,
    ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’,
    ‘SET_GROWABLE_BIT’, ‘SET_OBJECT’, ‘SET_TRUELENGTH’, ‘STRING_PTR’
These entry points may be removed soon:
‘EXTPTR_PROT’, ‘EXTPTR_TAG’, ‘FRAME’, ‘HASHTAB’, ‘BODY’, ‘FORMALS’, ‘CLOENV’, ‘ENCLOS’, ‘OBJECT’, ‘SET_FORMALS’, ‘SET_BODY’, ‘SET_CLOENV’, ‘STRING_PTR’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
  guess_tspec.Rd: abort
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
File 'tibblify/libs/x64/tibblify.dll':
  Found non-API calls to R: 'BODY', 'CLOENV', 'ENCLOS', 'EXTPTR_PROT',
    'EXTPTR_TAG', 'FORMALS', 'FRAME', 'HASHTAB', 'OBJECT', 'PRENV',
    'PRVALUE', 'R_PromiseExpr', 'Rf_allocSExp', 'Rf_findVarInFrame3',
    'SETLENGTH', 'SET_BODY', 'SET_CLOENV', 'SET_FORMALS',
    'SET_GROWABLE_BIT', 'SET_OBJECT', 'SET_TRUELENGTH', 'STRING_PTR'
These entry points may be removed soon:
'EXTPTR_PROT', 'EXTPTR_TAG', 'FRAME', 'HASHTAB', 'BODY', 'FORMALS', 'CLOENV', 'ENCLOS', 'OBJECT', 'SET_FORMALS', 'SET_BODY', 'SET_CLOENV', 'STRING_PTR'

Compiled code should not call non-API entry points in R.

See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
  guess_tspec.Rd: abort
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
File ‘tibblify/libs/tibblify.so’:
  Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘ENCLOS’, ‘EXTPTR_PROT’,
    ‘EXTPTR_TAG’, ‘FORMALS’, ‘FRAME’, ‘HASHTAB’, ‘OBJECT’, ‘PRENV’,
    ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’,
    ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’,
    ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’, ‘STRING_PTR’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
  guess_tspec.Rd: abort
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
File ‘tibblify/libs/tibblify.so’:
  Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘ENCLOS’, ‘EXTPTR_PROT’,
    ‘EXTPTR_TAG’, ‘FORMALS’, ‘FRAME’, ‘HASHTAB’, ‘OBJECT’, ‘PRENV’,
    ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’,
    ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’,
    ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’, ‘STRING_PTR’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
File ‘tibblify/libs/tibblify.so’:
  Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘ENCLOS’, ‘EXTPTR_PROT’,
    ‘EXTPTR_TAG’, ‘FORMALS’, ‘FRAME’, ‘HASHTAB’, ‘OBJECT’, ‘PRENV’,
    ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’,
    ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’,
    ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’, ‘STRING_PTR’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
File ‘tibblify/libs/tibblify.so’:
  Found non-API calls to R: ‘BODY’, ‘CLOENV’, ‘ENCLOS’, ‘EXTPTR_PROT’,
    ‘EXTPTR_TAG’, ‘FORMALS’, ‘FRAME’, ‘HASHTAB’, ‘OBJECT’, ‘PRENV’,
    ‘PRVALUE’, ‘R_PromiseExpr’, ‘Rf_allocSExp’, ‘Rf_findVarInFrame3’,
    ‘SETLENGTH’, ‘SET_BODY’, ‘SET_CLOENV’, ‘SET_FORMALS’,
    ‘SET_GROWABLE_BIT’, ‘SET_TRUELENGTH’, ‘STRING_PTR’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
  guess_tspec.Rd: abort
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
File 'tibblify/libs/x64/tibblify.dll':
  Found non-API calls to R: 'BODY', 'CLOENV', 'ENCLOS', 'EXTPTR_PROT',
    'EXTPTR_TAG', 'FORMALS', 'FRAME', 'HASHTAB', 'OBJECT', 'PRENV',
    'PRVALUE', 'R_PromiseExpr', 'Rf_allocSExp', 'Rf_findVarInFrame3',
    'SETLENGTH', 'SET_BODY', 'SET_CLOENV', 'SET_FORMALS',
    'SET_GROWABLE_BIT', 'SET_TRUELENGTH', 'STRING_PTR'

Compiled code should not call non-API entry points in R.

See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.