2026-06-15 — Last Week in Carbon #7360
josh11b
announced in
Last Week in Carbon
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Updates on leads issues
Updates on proposals
Updates on moderation across our community spaces (Discord and GitHub)
Activity on toolchain
testdata?selfbyref.onlybounds: New ideas on Rust traits that are included by default (traits that are excluded/negative traits) likeSized.carbon buildsubcommand in #7239 #7321selfto the explicit () parameter list (proposal #7016) in #7272Core.CharLiteralin #7316Activity about
.Selfin facet types.Selfin a nested/disconnected facet type as a greater distance along a separate axis compared to.Selfin a connected nested facet type (such as on the RHS of animplsconstraint, or on the LHS of awhere).eval fnreturning a facet type that makes it seemingly impossible to know what the.Selfit’s returning should be referring to.Selfdistance in nested/disconnected facet types, then do the same increment when substing.Self..Selfin a nested disconnected facet type, going to try doing it for all nested facet types..Self, which means its distance is not increased..Selfis a problem because you can always use interface calls to increment the distance of your current.Selfand create a collision:Z(Z(Z(.Self)))adds distance 3..Selfat itswhere. This is an example of what could be considered an ambiguous.Self, since it introduces a second.Selfvalue into the type..Selfnumbering problem, which constructs a type with two different.Selfinside. One use of the outer.Selfneeds to be incremented, the other use not..Selfin a type essentially leads to us having to solve lambda calculus (where.Selfis a free variable). Should we get rid of.Self?.Self..Selfambiguity rule. Any way to introduce a second value of.Selfleads to complexity that is too expensive/difficult to resolve, and thus ends up in crashes or coherence issues. This includes preventing ambiguity through internally representing rewrite designators with.Self.Activity on memory safety
ownedplace sets, invalidation, andaliases of place setsOther active discussions
These include Discord Chat, GitHub Discussions, or open discussion sessions.
ty. #7326 and #7331 may help.Coreand the prelude work? How about libraries in general? Should the prelude be a separate package from the rest ofCore?RSS Feed for "Last Week in Carbon" here
All reactions