🚀 go-pugleaf

I wish the byte-compiler gave us more control over the compilation
environment.  For example, if I define a defstruct-like macro, where
(my-defstruct foo slot-1 slot-2) expands into something like
(progn
  (defmacro foo-slot-1 (x) (list 'aref x 0))
  (defmacro foo-slot-2 (x) (list 'aref x 1)))
and, in the same file, I make use of the foo-slot-1 macro, that file
cannot be byte-compiled without loading it first, because the byte-
compiler does not expand top-level calls to macros (and consequently
evaluate any defmacros in the expansion).

Also, I have some code that can interface with a certain package if
that package is around.  If this is to be done, that package must be
loaded at compile time (because of macros) but if the package cannot
be loaded, that's ok (the interface to it just won't be used).
This means I'd like to have something like
	(condition-case c 
	    (require 'foobar) 
	  (error nil))
evaluated at compile-time.  Currently there is no way to specify
that arbitrary forms should be evaluated at compile-time; defmacros
and requires are special-cased when they appear at top-level.  
Something like Common Lisp's (eval-when (load eval compile) ... ) 
idiom is needed.

		-- Jamie