Recursive calls raise errors with @jitclass (but not @jit)

[allComputableThings]

Feature request

Reporting a bug

• [*] I am using the latest released version of Numba (most recent is visible in
  the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG). numba-0.38.1

• [*] I have included below a minimal working reproducer (if you are unsure how
  to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

@numba.jit
def x(i):
    if i>0:
        x(i-1)

@numba.jitclass(())
class C(object):
    def __init__(self):
        pass

    def x(self, i):
        if i>0:
            self.x(i-1)
x(6) # OK
C().x(6)  # Fail

Since recursive calls work for @jit functions, I'd think they'd work for @jitclass methods. Instead they raise:

  compiler re-entrant to the same function signature

[aldanor]

Wondering if there's any chance for this to be resolved?

Currently you have to run a bunch of ugly external functions to work around this and/or stop using jitclasses.

[joefutrelle]

@aldanor can you detail some of the workarounds you used? I need this capability and it looks like this issue is not close to resolution.

[juliusbierk]

Bump.

[eiis1000]

Any updates? This seems like a pretty important feature to not be supported