Skip to content

[ refactor ] ScopedSnocList: Preparing for the long jump (Phase 1) #3512

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

GulinSS
Copy link

@GulinSS GulinSS commented Mar 19, 2025

Core idea is to split the process of transition from List-based Scope on SnocList-based Scope on 2 phases:

  1. Apply a refactor which does not make any transition (even no observable changes for Idris users) actually but prepare the code for future update.
  2. Roll out the transition with limited code changes invasion because it was partially done at the step before.

Core idea is to split the process of transition from List-based Context on SnocList-based Context on 2 phases:

1. Apply a refactor which does not make any transition (even no observable changes for Idris users) actually but prepare the code for future update.
2. Roll out the transition with limited code changes invasion because it was partially done at the step before.

Co-authored-by: Viktor Yudov <[email protected]>
@GulinSS GulinSS force-pushed the scoped-snoc-list-preparing branch from a8c6014 to f7bc725 Compare March 24, 2025 17:15
@gallais
Copy link
Member

gallais commented Mar 24, 2025

Thanks for that.

FYI we (including at least @mjustus & me) are planning to do a big code review
on this PR on April 2nd with the hope it can quickly be merged afterwards.

@GulinSS
Copy link
Author

GulinSS commented Mar 25, 2025

@gallais much appreciate! 😇

@GulinSS
Copy link
Author

GulinSS commented Apr 3, 2025

@gallais, @mjustus shy reminder about the review and its importance! 🙏

We are going to make further steps of adding parts from Yaffle when this PR and its companion will succeed.

All this is a refactor which is important but these steps actually are preparations for something which can be added to the change log . And this step is scheduled to start the development after these 2 phases.

So, moving forward here is a corner stone to unlock further Idris improvements. All this is clear for invited people just it seemed important to explicitly emphasize at the message due of questions at Discord group.

@gallais
Copy link
Member

gallais commented Apr 3, 2025

We went through about a 3rd of the files. There a semantic issues (e.g. some lists of values being
made Scopeable even though they have nothing to do with Scopes) and we wanted to clarify some
things outside of the diff boundaries so started a fork of the fork.

@GulinSS
Copy link
Author

GulinSS commented Apr 11, 2025

@gallais any news would be very appreciate! We are in progress of porting other parts from Yaffle and pretty worried of possible changes 😅

It would be nice if you can put a link to PR/commits/branch/anything where we might participate during the review process. If it is needed of course.

@gallais
Copy link
Member

gallais commented Apr 11, 2025

Ping @mjustus

We haven't had the opportunity to have another meeting yet. And with
a conference happening this week it may not happen for another couple
of weeks either.

@GulinSS GulinSS force-pushed the scoped-snoc-list-preparing branch from f7bc725 to 3decb09 Compare April 15, 2025 08:22
@GulinSS
Copy link
Author

GulinSS commented Apr 16, 2025

@GulinSS GulinSS force-pushed the scoped-snoc-list-preparing branch 2 times, most recently from e5faef5 to 34ebbf0 Compare April 21, 2025 13:28
@gallais
Copy link
Member

gallais commented Apr 30, 2025

We met up today (thanks Justus for your hospitality!) and we've made good progress.
We have looked at about 75/103 files meaning we should be done by the end of our
next meeting in 2 weeks time.

@GulinSS GulinSS force-pushed the scoped-snoc-list-preparing branch from 34ebbf0 to c3a8909 Compare May 12, 2025 11:41
@mjustus
Copy link
Collaborator

mjustus commented May 14, 2025

I have pushed your current state to branch snoc-list-preparing-force-pushed on my copy of the repository and am about to revert this branch to f7bc725 because it was getting too difficult reviewing a moving target with large merge conflict.

@mjustus mjustus force-pushed the scoped-snoc-list-preparing branch from c3a8909 to f7bc725 Compare May 14, 2025 16:04
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.

3 participants