KPGPMC/furlang
5
3
Fork 2
Code Issues 11 Pull Requests Actions Packages Projects 3 Releases Wiki Activity

the great refactor #12

New Issue
Closed
opened 2026-06-15 18:20:02 +00:00 by CHatingPython · 0 comments
CHatingPython commented 2026-06-15 18:20:02 +00:00
Owner
Copy Link
Copy Source

The current state of furvm and furc is dissatisfying.
The refactor must:

  • rename furlang's IR module to mod to avoid C++20 collisions
  • render module creation independent of bytecode in furvm's API
  • improve the furvm's object API
  • improve the furlang's IR API
  • improve the furc's SSA class
  • improve furvm object serialization and deserialization
  • add missing quality of life functions to each API
The current state of furvm and furc is dissatisfying. The refactor must: - rename furlang's IR module to `mod` to avoid C++20 collisions - render module creation independent of bytecode in furvm's API - improve the furvm's object API - improve the furlang's IR API - improve the furc's SSA class - improve furvm object serialization and deserialization - add missing quality of life functions to each API
CHatingPython self-assigned this 2026-06-15 18:20:02 +00:00
CHatingPython added the Kind/Enhancement
Priority
High
2
 labels 2026-06-15 18:26:54 +00:00
CHatingPython added this to the v0.6.7 milestone 2026-06-15 18:26:58 +00:00
CHatingPython added reference great-refactor 2026-06-16 09:26:06 +00:00
CHatingPython added this to the furvm project 2026-06-19 12:08:20 +00:00
CHatingPython moved this to In Progress in furvm on 2026-06-19 12:08:44 +00:00
CHatingPython modified the project from furvm to furc 2026-06-21 18:45:06 +00:00
CHatingPython modified the project from furc to furvm 2026-06-21 18:45:09 +00:00
CHatingPython removed this from the furvm project 2026-06-21 18:45:20 +00:00
Sign in to join this conversation.
great-refactor
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label Kind/Enhancement
Priority
High
2
Milestone
No items
No Milestone v0.6.7
Projects
Clear projects
No project
Assignees
Clear assignees
admin CHatingPython (Aleksander Krajewski) femkromek FirstSecretary zlotowek
No Assignees CHatingPython
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KPGPMC/furlang#12
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?