PlexSheep
/
numf
Archived
generated from PlexSheep/rs-base
1
1
Fork 0
Code Issues 2 Pull Requests 1 Actions Packages Projects Releases 8 Wiki Activity

numf_parser panics with usize / does not compile with usize #22

New Issue
Closed
opened 2024-05-23 00:21:12 +02:00 by PlexSheep · 3 comments
PlexSheep commented 2024-05-23 00:21:12 +02:00
Owner
Copy Link
No description provided.
PlexSheep added the
Kind/Breaking
Kind/Bug
Priority
High
Reviewed
Confirmed
 labels 2024-05-23 00:21:12 +02:00
PlexSheep commented 2024-05-23 00:21:35 +02:00
Author
Owner
Copy Link

limitation in libpt, will need to fix upstream

limitation in libpt, will need to fix upstream
PlexSheep commented 2024-05-23 13:12:41 +02:00
Author
Owner
Copy Link

We have a test testing for this (parser_generics), but it does not test for usize. usize is the only affected unsigned int.

We have a test testing for this (`parser_generics`), but it does not test for `usize`. `usize` is the only affected unsigned int.
PlexSheep changed title from numf_parser only uses u128 despite generic, panics with other types to numf_parser panics with `usize` / does not compile with `usize` 2024-05-23 13:13:13 +02:00
PlexSheep commented 2024-05-23 13:15:51 +02:00
Author
Owner
Copy Link

This makes sense, as usize is guaranteed to be at least a 16 bit unsigned integer, but has no guaranteed max value. THerefore, in the future it could be larger than u128 (on 256-bit systems.). usize is the size of a pointer on the OS.

This makes sense, as `usize` is guaranteed to be at least a 16 bit unsigned integer, but has no guaranteed max value. THerefore, in the future it could be larger than `u128` (on 256-bit systems.). `usize` is the size of a pointer on the OS.
PlexSheep added
Reviewed
Won't Fix
 and removed
Reviewed
Confirmed
 labels 2024-05-23 13:16:24 +02:00
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
master
devel
feat/guess-format
v0.4.1
v0.4.0
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.0
v0.1.0
Labels
Clear labels   
Kind/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
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Reviewed
Confirmed
Issue has been confirmed

  
Reviewed
Duplicate
This issue or pull request already exists

  
Reviewed
Invalid
Invalid issue

  
Reviewed
Won't Fix
This issue won't be fixed

  
Status
Abandoned
Somebody has started to work on this but abandoned work

  
Status
Blocked
Something is blocking this issue or pull request

  
Status
Need More Info
Feedback is required to reproduce issue or to continue work

No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: PlexSheep/numf#22
No description provided.
Delete Branch "%!s(<nil>)"

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?