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

feat: introduce pointer thing type #35

New Issue
Closed
opened 2026-06-29 14:36:47 +00:00 by CHatingPython · 3 comments
CHatingPython commented 2026-06-29 14:36:47 +00:00
Owner
Copy Link
Copy Source

Introduce pointer thing type for FFI.

Introduce pointer thing type for FFI.
CHatingPython added this to the v0.6.7 milestone 2026-06-29 14:36:47 +00:00
CHatingPython added the Kind/Feature
Priority
High
2
 labels 2026-06-29 14:36:47 +00:00
CHatingPython self-assigned this 2026-06-29 14:36:47 +00:00
CHatingPython added this to the furvm project 2026-06-29 14:36:47 +00:00
CHatingPython moved this to To Do in furvm on 2026-06-29 14:36:52 +00:00
CHatingPython commented 2026-07-04 14:17:46 +00:00
Author
Owner
Copy Link
Copy Source

I've changed my mind and will no longer make a separate type type for a pointer, instead pointers will be in the core module as an alias to long for now.

I've changed my mind and will no longer make a separate type type for a pointer, instead pointers will be in the core module as an alias to long for now.
CHatingPython moved this to Done in furvm on 2026-07-04 14:17:55 +00:00
CHatingPython moved this to To Do in furvm on 2026-07-06 20:08:26 +00:00
CHatingPython commented 2026-07-06 20:08:44 +00:00
Author
Owner
Copy Link
Copy Source

Nevermind, pointer types will be useful :3

Nevermind, pointer types will be useful :3
CHatingPython moved this to In Progress in furvm on 2026-07-07 22:25:35 +00:00
CHatingPython commented 2026-07-07 22:32:17 +00:00
Author
Owner
Copy Link
Copy Source

Never mind, they should be type attributes (like references) but I don't care enough to implement them right now.

Never mind, they should be type attributes (like references) but I don't care enough to implement them right now.
CHatingPython moved this to Backlog in furvm on 2026-07-07 22:32:23 +00:00
CHatingPython moved this to Done in furvm on 2026-07-07 22:32:31 +00:00
CHatingPython moved this to In Progress in furvm on 2026-07-09 20:04:48 +00:00
CHatingPython moved this to To Do in furvm on 2026-07-10 12:45:13 +00:00
CHatingPython moved this to In Progress in furvm on 2026-07-11 00:29:22 +00:00
CHatingPython moved this to Done in furvm on 2026-07-11 20:44:55 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
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/Feature
Priority
High
2
Milestone
No items
No Milestone v0.6.7
Projects
Clear projects
No project furvm
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#35
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?