GetFirefly/firefly

Undocumented BIFs

Open

#188 opened on Jun 7, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (110 forks)github user discovery
enhancementhelp wantedruntime/bifs

Repository metrics

Stars
 (3,591 stars)
PR merge metrics
 (PR metrics pending)

Description

Determine whether these BIFs are undocumented, but called by Erlang code, so necessary for us to implement or if they are an implementation detail of the BEAM and can be ignored.

  • crasher/6
  • delay_trap/2
  • dt_append_vm_tag_data/1
  • dt_get_tag/0
  • dt_get_tag_data/0
  • dt_prepend_vm_tag_data/1
  • dt_put_tag/1
  • dt_restore_tag/1
  • dt_spread_tag/1
  • exit_signal/2
  • get_module_info/1
  • get_module_info/2
  • subtract/2

Contributor guide

Research direction
For each BIF in the list, search the Erlang/OTP source code to see if it is called. If it is called, it needs to be implemented; otherwise, it may be an internal BEAM detail. Start by examining `crasher/6` and `delay trap/2` as they are likely called.
Tech stack
rust
Domain
backend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustErlang/BEAM
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50