Search results

user-defined opDefs in a user package can't be located (with a proposed solution)

Status: Open.

#118 In nimble-dev/nCompiler;

· paciorek opened on Feb 10, 2026

discussion of opDef provided to an nFunction

Status: Open.

#117 In nimble-dev/nCompiler;

· paciorek opened on Feb 10, 2026

checking deduced types

Status: Open.

#116 In nimble-dev/nCompiler;

· paciorek opened on Feb 7, 2026

compilation order untrapped C++ compilation exception

bugSomething isn't workingSomething isn't working

Status: Open.

#114 In nimble-dev/nCompiler;

· paciorek opened on Feb 7, 2026

for loop operator

Status: Open.

#113 In nimble-dev/nCompiler;

· paciorek opened on Feb 3, 2026

should we use portable R6 classes?

Status: Open.

#112 In nimble-dev/nCompiler;

· paciorek opened on Feb 3, 2026

enhance compiler with ability to handle nCompiler namespace resolution for more flexibility for dependent packages

enhancementNew feature or requestNew feature or request

Status: Open.

#111 In nimble-dev/nCompiler;

· paciorek opened on Feb 2, 2026

writing user packages that depend on nCompiler: summary

Status: Open.

#110 In nimble-dev/nCompiler;

· paciorek opened on Feb 2, 2026

need R versions of various operators

Status: Open.

#109 In nimble-dev/nCompiler;

· paciorek opened on Jan 28, 2026

gracefully trap incorrect returnType in <code>nCompile</code>

Status: Open.

#107 In nimble-dev/nCompiler;

· paciorek opened on Jan 25, 2026

char type not handled by compiler

Status: Open.

#106 In nimble-dev/nCompiler;

· paciorek opened on Jan 25, 2026

should we mimic the R6 API more?

Status: Open.

#104 In nimble-dev/nCompiler;

· paciorek opened on Jan 23, 2026