Rhombus bi-weekly virtual meeting #180
Replies: 53 comments 74 replies
-
Plan for September 30: brief intro and then work through #122. The idea is that digesting the details of a proposal takes time, but working through one as a group can make things more clear and aid further discussion. |
Beta Was this translation helpful? Give feedback.
-
Minor scheduling announcement: Matthew and I decided to have meetings on a once-every-other-week basis rather than once a week. So after today's meeting, the next meeting will be on October 28th. I've added a calendar event anyone can invite themselves to here. Today's agenda: I've drafted a State of Rhombus document. We can discuss it today and hopefully publish it more widely after a few rounds of comments. |
Beta Was this translation helpful? Give feedback.
-
Agenda for today's meeting: we'll start with the updated State of Rhombus document, based on the previous meeting, and then start talking about pieces of Rhombus that people are interested in working on. |
Beta Was this translation helpful? Give feedback.
-
Agenda for today's meeting:
|
Beta Was this translation helpful? Give feedback.
-
We are meeting today! Agenda:
|
Beta Was this translation helpful? Give feedback.
-
Some discussion points for tomorrow's meeting, December 16:
Given the upcoming holidays, out meeting after this one will be January 6 (instead of December 30). |
Beta Was this translation helpful? Give feedback.
-
For January 6th, I'm interested in attending... I kicked up some dust recently about surface syntax decisions and there was expression of interest on today's call about discussing this at the next meeting. I also offered to help turn the wraith writeup into a proper proposal before the meeting, though I think I'd appreciate some help with that (which @AlexKnauth said they probably could do though it was not their primary focus at the moment). |
Beta Was this translation helpful? Give feedback.
-
Agenda for the January 6 meeting this week:
|
Beta Was this translation helpful? Give feedback.
-
Our next meeting is this Thursday, January 20. As a starting point for discussion, let's take up the question of iteration/comprehension syntax (along the lines of |
Beta Was this translation helpful? Give feedback.
-
If I understand "specialization of equal-always" correctly @mflatt, then this is exactly what my proposal earlier was about (for reference). I haven't had a chance to return to it, but to summarize in this context, the idea is that instead of relying on users to do:
or
we instead bake the mapping function into a higher level equality interface
This == becomes pervasive in all equality-related notions throughout the language, e.g. hashes, sequence interfaces that leverage equality (e.g. index-of, remove, replace, ...), always expose a
And the second Alice overwrites the first since this hash is case insensitive. I don't think there would be any performance related issues here because every case where we use a key function is a case where we would use one anyway. prop:hash issues also don't come in (which I think you pointed out, Matthew) because the ultimate hash used is simply the one defined in equal-always after applying the mapping function. The question is just whether we choose to incorporate the notion of a key function into the equality interface presented by the language or leave it to users to do it in an ad hoc way. I see advantages to baking it into the equality interface which I mentioned earlier, viz. a single interface usable in all cases by virtue of mapping functions being able to express any notion / specialization of equality. It would also have the effect of eliminating the need for a large number of predicates, such as string-ci=?, and the need for users to define custom binary equality lambdas for use with interfaces like To be clear, there isn't a single mapping function being talked about here but simply a If my attendance at an upcoming meeting would be useful then I can aim to attend, let me know 👍 |
Beta Was this translation helpful? Give feedback.
-
@mflatt I'd love to join an upcoming meeting to discuss the interface to elementary relations such as |
Beta Was this translation helpful? Give feedback.
-
Our next meeting is today, Thursday, February 3. Initial agenda:
|
Beta Was this translation helpful? Give feedback.
-
We meet today, February 17. The topic is: experience writing Rhombus macros, so far, and discussion on how it could be easier/better. |
Beta Was this translation helpful? Give feedback.
-
We'll meet today, March 3. There's a not a specific agenda this time, but we can discuss the current status and plans. |
Beta Was this translation helpful? Give feedback.
-
We can start tomorrow's meeting (March 17) with ideas and discussion on #213. The U.S. has switched to Daylight Saving time since the last meeting, so please check the mapping of 2:00 PM MDT to your time zone. |
Beta Was this translation helpful? Give feedback.
-
Agenda for the August 3 meeting: Sam Phillips will demo some of his Rhombus code. If there's time, I can show some parts of Shplait's implementation in Rhombus. |
Beta Was this translation helpful? Give feedback.
-
can the demo component be recorded?
I can't join - but I have a good excuse as it is Miriams birthday
s.
…On Wed, Aug 2, 2023 at 10:13 PM Matthew Flatt ***@***.***> wrote:
Agenda for the *August 3* meeting: Sam Phillips will demo some of his
Rhombus code. If there's time, I can show some parts of Shplait's
implementation in Rhombus.
—
Reply to this email directly, view it on GitHub
<#180 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2MD3DAGCC6PAZVKWLCJ3XTK7GTANCNFSM5EUA5MHQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
Bit of a silly question, but does Rhombus have a logo? |
Beta Was this translation helpful? Give feedback.
-
Hi
‘Rhombus’ is a placeholder for a name to be agreed later:
"Rhombus" is the name of the project that will develop a language, and "Rhombus" is a temporary stand-in for a language name to be determined later. Phase 3 of the plan includes the mandatory step of picking a new language name.
https://github.com/racket/rhombus-prototype/blob/master/resources/plan.md#rhombus-plan
The project is currently in Phase 2 as described in the link above
Best regards
Stephen
On Fri, 4 Aug 2023 at 05:48, Ashton Wiersdorf ***@***.***> wrote:
Bit of a silly question, but does Rhombus have a logo?
—
Reply to this email directly, view it on GitHub
<#180 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2MD4DSBU3BKSCDFAMRI3XTR5H7ANCNFSM5EUA5MHQ>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
--
----
|
Beta Was this translation helpful? Give feedback.
-
Sorry for not sending out this message earlier, but we will meet as usual at 4 PM Eastern. |
Beta Was this translation helpful? Give feedback.
-
Agenda for the August 31 meeting: We are currently in the "Phase 2: Iterative Design" step of the Rhombus Plan. What will it take to get to the "Phase 3: Conversion" step? |
Beta Was this translation helpful? Give feedback.
-
In the September 14 meeting, we'll discuss types. |
Beta Was this translation helpful? Give feedback.
-
The list design in #351 is ready for review and a good topic for the next meeting. |
Beta Was this translation helpful? Give feedback.
-
No meeting November 23, which would be our normally scheduled next meeting, due to the U.S. holiday. I suggest that we delay only by one week and meet on November 30. That does shift our meeting schedule, though, so let me know if that creates trouble. |
Beta Was this translation helpful? Give feedback.
-
For the November 30 meeting, we'll start with a report from Alec on the RRB tree implementation. |
Beta Was this translation helpful? Give feedback.
-
Notes from today's (2023/12/14) meeting: I talked about some observations from doing some Advent of Code puzzles with Rhombus recently:
@mflatt needed to leave early and @AlexKnauth joined late so in the second half of the meeting we talked about using the at notation to make format strings.
|
Beta Was this translation helpful? Give feedback.
-
We'll take a break for holidays, so the next meeting is January 11. Also, we'll switch back to 6:00pm Mountain Time (instead of 2:00pm), so that it's a reasonable time of day for @usaoc. |
Beta Was this translation helpful? Give feedback.
-
Notes on the February 22 meeting Some general Rhombus things that need more work or discussion:
Thoughts on the
|
Beta Was this translation helpful? Give feedback.
-
Plan for the March 21 meeting: Cooper will present his background work and initial design for a regexp sublanguage. |
Beta Was this translation helpful? Give feedback.
-
Notes from the April 4 meeting: Besides discussing recent changes and pull requests to make sure we agree, we tried to make a list of things that we'd like to finish or clean up before moving the next Rhombus stage:
For enumerations, the idea from the meeting did not work out well when I tried it. PR #497 is what I found to work well in practice, which is to have long names for use in contexts where it's worthwhile for checking, but to generally use symbols for brevity. |
Beta Was this translation helpful? Give feedback.
-
Let's try a regular Rhombus virtual meeting, open to anyone interested.
The next meeting is on May 30.
When: Every other Thursday at 7:00 pm Mountain Time, which is also
Where: https://utah.zoom.us/j/96590513005
What:
History: Meeting time was 2:00pm Mountain Time before August 4, 2022, then 6:00pm Mountain Time until July 20, 2023, then back to 2:00pm Mountain Time until January 11, 2024, then back to 6:00pm Mountain Time until April 3, 2024, then to 7:00pm Mountain Time.
Beta Was this translation helpful? Give feedback.
All reactions