vyperlang/vyper

missing compile-time evaluation for `convert`, `slice` and `extract32`

Open

#2,498 opened on Oct 20, 2021

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Python (4,710 stars) (849 forks)batch import
Easy PickingsOptimizationhelp wanted

Description

How to fix it

Add def evaluate() implementations to the objects in https://github.com/vyperlang/vyper/blob/e9b9aff85b315371a21b574406cf8a4601ecc779/vyper/builtin_functions/functions.py

Contributor guide

Tech stack
python
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with Vyper compilerPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
The issue asks to add `def evaluate()` methods to the `convert`, `slice`, and `extract32` objects in the file `vyper/builtin functions/functions.py`. Start by examining existing `evaluate()` implementations in that file to understand the pattern. Then, implement compile time evaluation for each function, ensuring the method returns a valid AST node or raises an error if evaluation is not possible. Consult the comments in the linked GitHub issue for any additional guidance.