valhalla-spec-experts  

Messages by Thread

• Anonymous value classes Dan Smith
  • Re: Anonymous value classes Dan Smith
  • Re: Anonymous value classes Remi Forax
  • Re: Anonymous value classes Brian Goetz
  • Re: Anonymous value classes Remi Forax
  • Re: Anonymous value classes Brian Goetz
  • Re: Anonymous value classes Maurizio Cimadamore
  • Re: Anonymous value classes forax
  • Re: Anonymous value classes Dan Smith
  • Re: Anonymous value classes forax
• EG meeting *canceled*, 2022-06-01 Dan Smith
• EG meeting, 2022-05-18 Dan Smith
  • Re: EG meeting, 2022-05-18 Dan Smith
• User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Dan Heidinga
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Dan Smith
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Dan Smith
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Kevin Bourrillion
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Kevin Bourrillion
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Dan Smith
  • Re: User model stacking: current status Remi Forax
  • Re: User model stacking: current status Brian Goetz
  • Nullity (was: User model stacking: current status) Brian Goetz
  • Re: Nullity (was: User model stacking: current status) Kevin Bourrillion
  • Re: Nullity (was: User model stacking: current status) Brian Goetz
  • Re: Nullity (was: User model stacking: current status) Kevin Bourrillion
  • Re: Nullity (was: User model stacking: current status) Brian Goetz
  • Re: Nullity (was: User model stacking: current status) Dan Smith
  • Re: Nullity (was: User model stacking: current status) Brian Goetz
  • Re: Nullity (was: User model stacking: current status) Kevin Bourrillion
  • Re: Nullity (was: User model stacking: current status) Kevin Bourrillion
  • Re: Nullity (was: User model stacking: current status) Brian Goetz
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Remi Forax
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Remi Forax
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Dan Heidinga
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status forax
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Dan Heidinga
  • Re: User model stacking: current status Brian Goetz
  • Re: User model stacking: current status Dan Heidinga
  • Re: User model stacking: current status Dan Heidinga
  • Re: User model stacking: current status Brian Goetz
• User model: terminology Brian Goetz
  • Re: User model: terminology Remi Forax
  • Re: [External] : Re: User model: terminology Brian Goetz
  • Re: User model: terminology Kevin Bourrillion
  • Re: User model: terminology forax
  • Re: User model: terminology Kevin Bourrillion
  • Re: [External] : Re: User model: terminology Brian Goetz
  • Re: [External] : Re: User model: terminology Brian Goetz
  • Re: [External] : Re: User model: terminology Brian Goetz
• EG meeting, 2022-05-04 Dan Smith
  • Re: EG meeting, 2022-05-04 Kevin Bourrillion
  • Re: EG meeting, 2022-05-04 John Rose
• User model: ref as default, vs universal generics Brian Goetz
• Spec change documents for Value Objects Dan Smith
  • Re: Spec change documents for Value Objects Dan Smith
• User model stacking Brian Goetz
  • Re: User model stacking Remi Forax
  • Re: User model stacking Dan Heidinga
  • Re: User model stacking Remi Forax
  • Re: [External] : Re: User model stacking Brian Goetz
  • Re: [External] : Re: User model stacking Brian Goetz
  • Re: [External] : Re: User model stacking John Rose
  • Re: [External] : Re: User model stacking Brian Goetz
  • Re: [External] : Re: User model stacking Brian Goetz
  • Re: [External] : Re: User model stacking Remi Forax
  • Re: [External] : Re: User model stacking Brian Goetz
  • Re: [External] : Re: User model stacking forax
  • Re: [External] : Re: User model stacking Kevin Bourrillion
  • Re: [External] : Re: User model stacking Maurizio Cimadamore
  • Re: [External] : Re: User model stacking forax
  • Re: [External] : Re: User model stacking Brian Goetz
  • Re: [External] : Re: User model stacking Dan Heidinga
  • Null channels (was: User model stacking) Brian Goetz
  • Re: Null channels (was: User model stacking) Remi Forax
  • Re: User model stacking Kevin Bourrillion
  • Re: User model stacking Kevin Bourrillion
  • Re: User model stacking Dan Smith
  • Re: User model stacking Brian Goetz
• On tearing Brian Goetz
  • Re: On tearing Remi Forax
  • Re: [External] : Re: On tearing Brian Goetz
  • Re: [External] : Re: On tearing John Rose
  • Re: On tearing Dan Heidinga
• We need help to migrate from bucket 1 to 2; and, the == problem Kevin Bourrillion
  • Re: We need help to migrate from bucket 1 to 2; and, the == problem Brian Goetz
  • Re: We need help to migrate from bucket 1 to 2; and, the == problem Kevin Bourrillion
  • Re: We need help to migrate from bucket 1 to 2; and, the == problem Dan Smith
  • Re: We need help to migrate from bucket 1 to 2; and, the == problem Kevin Bourrillion
  • Re: We need help to migrate from bucket 1 to 2; and, the == problem Kevin Bourrillion
  • Re: We need help to migrate from bucket 1 to 2; and, the == problem Dan Heidinga
  • Re: We need help to migrate from bucket 1 to 2; and, the == problem Kevin Bourrillion
  • Re: We need help to migrate from bucket 1 to 2; and, the == problem Remi Forax
• B3 ref model Remi Forax
  • Re: B3 ref model Dan Smith
  • Re: B3 ref model forax
  • Re: B3 ref model Brian Goetz
  • Re: B3 ref model forax
  • Re: B3 ref model Dan Smith
• Flattening to date Brian Goetz
• [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Brian Goetz
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Dan Heidinga
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Brian Goetz
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Dan Heidinga
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Brian Goetz
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Remi Forax
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Brian Goetz
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo forax
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Brian Goetz
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Dan Heidinga
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Dan Smith
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Dan Smith
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Brian Goetz
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Dan Smith
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Dan Heidinga
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Dan Smith
  • Re: [External] : Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Brian Goetz
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Dan Smith
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Remi Forax
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Brian Goetz
  • Re: [External] Foo / Foo.ref is a backward default; should be Foo.val / Foo Kevin Bourrillion
• Objects vs. values, the continuation Kevin Bourrillion
  • Re: Objects vs. values, the continuation Brian Goetz
  • Re: Objects vs. values, the continuation Remi Forax
  • Re: [External] : Re: Objects vs. values, the continuation Brian Goetz
  • Re: [External] : Re: Objects vs. values, the continuation forax
  • Re: Objects vs. values, the continuation Kevin Bourrillion
  • Re: [External] : Re: Objects vs. values, the continuation Brian Goetz
  • Re: Objects vs. values, the continuation Remi Forax
  • Re: Objects vs. values, the continuation Remi Forax
  • Re: Objects vs. values, the continuation Kevin Bourrillion
  • Re: Objects vs. values, the continuation forax
  • Re: Objects vs. values, the continuation Dan Heidinga
  • Re: Objects vs. values, the continuation Brian Goetz
  • 128bits value type and VarHande.compareAndSet() Was: Objects vs. values, the continuation Remi Forax
  • Re: Objects vs. values, the continuation Kevin Bourrillion
• EG meeting *canceled*, 2022-04-20 Dan Smith
• EG meeting, 2022-04-06 Dan Smith
• Object as a concrete class Dan Smith
  • Re: Object as a concrete class Kevin Bourrillion
  • Re: Object as a concrete class Brian Goetz
  • Re: Object as a concrete class Dan Heidinga
  • Re: [External] : Re: Object as a concrete class Brian Goetz
  • Re: [External] : Re: Object as a concrete class Dan Heidinga
  • Re: Object as a concrete class Remi Forax
  • Re: Object as a concrete class Kevin Bourrillion
• EG meeting, 2022-03-23 Dan Smith
• Alternative to IdentityObject & ValueObject interfaces Dan Smith
  • Re: Alternative to IdentityObject & ValueObject interfaces Dan Heidinga
  • Re: Alternative to IdentityObject & ValueObject interfaces Dan Smith
  • Re: Alternative to IdentityObject & ValueObject interfaces Dan Heidinga
  • Re: Alternative to IdentityObject & ValueObject interfaces Dan Smith
  • Re: Alternative to IdentityObject & ValueObject interfaces Kevin Bourrillion
  • Re: Alternative to IdentityObject & ValueObject interfaces Dan Smith
  • Re: Alternative to IdentityObject & ValueObject interfaces Maurizio Cimadamore
  • Re: Alternative to IdentityObject & ValueObject interfaces Remi Forax
  • Re: Alternative to IdentityObject & ValueObject interfaces Brian Goetz
  • Re: Alternative to IdentityObject & ValueObject interfaces Remi Forax
  • Re: Alternative to IdentityObject & ValueObject interfaces Dan Heidinga
  • Re: [External] : Re: Alternative to IdentityObject & ValueObject interfaces Brian Goetz
  • Re: Alternative to IdentityObject & ValueObject interfaces Dan Smith
  • Re: Alternative to IdentityObject & ValueObject interfaces Brian Goetz
  • Re: Alternative to IdentityObject & ValueObject interfaces Remi Forax
• EG meeting *canceled*, 2022-03-09 Dan Smith
• EG meeting, 2022-02-23 Dan Smith
• Evolving instance creation Dan Smith
  • Re: Evolving instance creation Dan Heidinga
  • Re: Evolving instance creation Remi Forax
  • Re: Evolving instance creation Dan Smith
  • Re: Evolving instance creation Brian Goetz
  • Re: Evolving instance creation Kevin Bourrillion
  • Re: Evolving instance creation Dan Smith
• Abstract class with fields implementing ValueObject Frederic Parain
  • Re: Abstract class with fields implementing ValueObject John Rose
  • Re: Abstract class with fields implementing ValueObject Remi Forax
  • Re: Abstract class with fields implementing ValueObject Dan Smith

• Earlier messages