NVIDIA / NVIDIA/cuda-quantum

Returning `None` is not supported kernel functions

Open
#1,657 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

python bridge stale-notified
Dominant language
C++
Stars
1.1k
Forks
456
Avg merge
1d 22h
Merged PRs (30d)
165

Description

Required prerequisites
  • Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
  • Make sure you've read the documentation. Your issue may be addressed there.
  • Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
  • If possible, make a PR with a failing test to give us a starting point to work on!
Describe the bug

Does not work

import cudaq
import numpy as np

@cudaq.kernel
def test_k() -> complex:
    return None

print(test_k()) # cudaq.kernel.ast_bridge.CompilerError: program.py:14: error: unhandled constant value (offending source -> None)

#Works

def test() -> complex:
    return None

print(test())
Steps to reproduce the bug
import cudaq
import numpy as np

@cudaq.kernel
def test_k() -> complex:
    return None

print(test_k())
Expected behavior

None is printed

Is this a regression? If it is, put the last known working version (or commit) here.

Not a regression

Environment
  • CUDA Quantum version:
  • Python version:
  • C++ compiler:
  • Operating system:
Suggestions

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the Python reproducer with the CUDA Quantum kernel decorator and inspect the compiler path that reports the unhandled constant value for None. Compare the decorated kernel with the ordinary Python function, then add coverage for returning None and verify that the expected behavior is produced.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, python
Domain
compilers
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.