Libraries do not collect binding metadata

[GoogleCodeExporter]

At least arguments could be collected easily, and same could be extended later 
if/when there is some type inference support.

 $ ol
 You see a prompt 
 > (define (foo a b) a)
 foo
 > foo
 ;; a b → ?
 #<foo>
 > (define-module foo (export bar) (define (bar x) x))
 module defined
 > (import foo bar)
 imported
 > bar
 ;; x → ? -- module foo
 #<bar>

where the the type signatures could be something like
 ;; x → ?        == run-of-the-mill continuation use
 ;; k x ⇒ (k ?)  == same with explicitly given continuation
 ;; x → x        == when there is a (checked) type definition available for the defn

Original issue reported on code.google.com by aohelin on 25 Dec 2011 at 9:55

[GoogleCodeExporter]

Original comment by aohelin on 25 Dec 2011 at 9:56

• Changed state: Meditate

[GoogleCodeExporter]

Issue 51 has been merged into this issue.

Original comment by aohelin on 4 Jan 2012 at 8:01

[GoogleCodeExporter]

Halfway added variable metadata collection to intern-thread before noticing 
anything wrong. The metadata should obviously be contained within the module or 
library, not separately like the interning which really does have to share some 
global info.

Original comment by aohelin on 8 Jan 2012 at 11:28

• Changed title: Modules do not collection any metadata

[GoogleCodeExporter]

swapped to libraries, since the old module system is being deprecated

Original comment by aohelin on 15 Jan 2012 at 10:20

• Changed title: Libraries do not collect binding metadata