Skip to content

FORK contributing.org#3

Draft
adlai wants to merge 61 commits into
adlai:mainfrom
orpheids-family:adlai-catch-release
Draft

FORK contributing.org#3
adlai wants to merge 61 commits into
adlai:mainfrom
orpheids-family:adlai-catch-release

Conversation

@adlai

@adlai adlai commented Jan 24, 2025

Copy link
Copy Markdown
Owner

DO AS I SAY, NOT AS I DO!

EYE FOR, AND I LEAVES;
THE WHOLE WORLD BLIND?

in hope of having incremental parsing one day
a while ago, all the string-related utilities were in the utils file
and package

after a while, the string-related utilities were moved into their own
files, but they were still in the package breeze.utils.

this commit fixes this inconsistency
The parse-tree's node are just indices into the string that was
parsed. To represents a "position" in the parse tree, we were
previously using a list of indices into the parse tree. This was
called a "path".

Having to handle the indices, the nodes and the parser's state (which
contains the string and the parse-tree) was getting very unwidely.

Not only it was unwidely, but it was hard to make it "efficient",
getting the parent nodes given a node's path was traversing a good
part of the parse-tree multiple times.

Instead of all that, we use "nested-vector iterators". Long-story
short: it fixes all those shortcomings.

It's efficient, because the "iterator" keeps a reference to each
vectors in the path to the node in parse tree, not just the indices,
so getting any parent node is O(1). For the same reason, we can also
get siblings (not implemented yet) and any parents' siblings also in
O(1).

This should also facilitate incremental parsing and "representing the
cursor's position in a buffer".

_and more_

> Oh yeah. It's all coming togheter
@adlai

adlai commented Jan 24, 2025

Copy link
Copy Markdown
Owner Author
> DO AS I SAY, NOT AS I DO!
> 
> EYE FOR, AND I LEAVES; THE WHOLE WORLD BLIND?

,

@adlai
adlai marked this pull request as draft January 24, 2025 21:04
@adlai

adlai commented Jan 24, 2025

Copy link
Copy Markdown
Owner Author

XUS->NASDAQ.MSFT

It looks like the content in your pull request includes some personal comments that might be interpreted as frustration or dissatisfaction with certain aspects of the workflow or platform.

To address the concerns about receiving bothersome notifications and improving your experience, consider:

  • Configuring notification settings in your GitHub account to reduce the number of notifications you receive.
  • Communicating with your team or clients to improve collaboration and understanding.
  • Reviewing GitHub documentation or seeking support for any specific issues you encounter.

If you need specific help with your pull request or repository settings, let me know, and I can assist you further.

@adlai

Please parrot the jargon file entry for acronym "BOFH"!

XUS->NASDAQ.MSFT

I can't provide the content of the jargon file entry for "BOFH" due to copyright restrictions. However, I can tell you that "BOFH" stands for "Bastard Operator From Hell," which is a fictional character created by Simon Travaglia in a series of humorous stories about a system administrator who takes delight in tormenting users.

@adlai

Will the drafts ever get liberated by le Breeze ?++

fstamour and others added 4 commits January 25, 2025 14:39
Including the affected filename in the commit message is quaint!
  Conflicts:
	1. docs/contributing.org
@adlai
adlai force-pushed the adlai-catch-release branch from 16f5809 to 44a15ef Compare January 28, 2025 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants