Feature: Parse floating point literals #13

Open
opened 2023-10-22 23:40:05 +00:00 by j · 0 comments
Owner

Feature Progress

  • Figure out what information is necessary to parse a floating point number
  • Find an open algorithm to parse a floating point number, add a citation in the source and documentation, and ensure we're following the license terms for it
  • Implement that algorithm in the Parser or Lexer

Feature description

Floating point numbers are vital to have in any programming context, due to their ability to hold a very large range of values in limited space. Parsing floating point literals is an important part of that; otherwise, we'll only be able to operate on floats produced by external code.

Example

0.1234567 // is a floating point number
1234567.0 // is a floating point number
# Feature Progress <!-- Describe the steps for implementing this feature in libconlang --> - [ ] Figure out what information is necessary to parse a floating point number - [ ] Find an open algorithm to parse a floating point number, add a citation in the source and documentation, and ensure we're following the license terms for it - [ ] Implement that algorithm in the Parser or Lexer # Feature description <!-- [Feature name] does a cool thing that you should describe here --> Floating point numbers are vital to have in any programming context, due to their ability to hold a very large range of values in limited space. Parsing floating point literals is an important part of that; otherwise, we'll only be able to operate on floats produced by external code. # Example <!-- Demonstrate this feature with a clear, concise code example Right now, we're (ab)using Rust syntax highlighting, since it most closely matches what I'm currently aiming for --> ```rust 0.1234567 // is a floating point number 1234567.0 // is a floating point number ```
j added the
enhancement
help wanted
labels 2023-10-22 23:40:05 +00:00
j added this to the Basic Syntax project 2023-10-22 23:40:05 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
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: j/Conlang#13
No description provided.