Difference between revisions of "What the JVM needs"

From JVMLangSummit
Jump to navigationJump to search
Line 4: Line 4:
 
* please optimize this
 
* please optimize this
 
* fences
 
* fences
* typestate: now immutable
+
* typestate: now immutable - especially arrays (typically encapsulated in non-writing header, a la java.lang.String)
 
* [[Why Tailcalls]]: as a guarantee, not just an optimization
 
* [[Why Tailcalls]]: as a guarantee, not just an optimization
  

Revision as of 11:40, 28 July 2010

Notes from Rich Hickey's workshop

user mode limitations

  • please optimize this
  • fences
  • typestate: now immutable - especially arrays (typically encapsulated in non-writing header, a la java.lang.String)
  • Why Tailcalls: as a guarantee, not just an optimization

numbers

  • fixnums
  • need a uniform entry/exit types (Object => boxing)
  • Hacker's delight overflow detection is OK (only for add/sub); need a static method that throws overflow-exception?

storage management

  • floating garbage foo(o, o=null); is tailcall a solution?

limits

  • 31-bit arrays
  • 16-bit instructions
  • static data structures (array literals)

types

  • structs, value types