Native function registration enhancement

Open
#27 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
62/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend

Research direction

Start by locating rune_attempt_register_native_functions and tracing how lazy initialization and imports reach it. Check how an existing native registration is represented, then verify that a custom implementation remains unchanged after a later import; add or run focused coverage for both first registration and attempted re-registration.

Written by the indexing model from the issue text.

Description

Feature Request

Description of Problem:

Currently, the rune_attempt_register_native_functions will set or overwrite the native function implementation.
As the initialisation is lazy, it could be misleading if a developer attempts to specify own native function implementation and the n later due to an import the stub redefines the custom installed native function to the system default one.

Potential Solutions:

rune_attempt_register_native_functions to check if the function is already registered and do not override if it is.

Dominant language
Python
Stars
0
Forks
3
Avg merge
5m
Merged PRs (30d)
1

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.

More from finos/rune-python-runtime

All issues in finos/rune-python-runtime

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.