[Xmonad] Issue 17 in project xmonad

codesite-noreply at google.com codesite-noreply at google.com
Fri Jun 1 01:29:56 EDT 2007


Issue 17: User-definable X monad state type
http://code.google.com/p/xmonad/issues/detail?id=17

Comment #1 by dons00:
We have two proposed solutions:

1), standard dynamically checked symbol table in XState. Using a Map String Dynamic
or similar, see [http://cse.unl.edu/~sjanssen/typekey.hs]. Used in Yi, notably, for
data type extensions. Upside: we know it works. Downside: runtime checking, urgh.

2) user-specified StateT types. Add a data type parameter to X, defined in Config.hs.
Upside: fully statically checked. Downside: combining state from separate plugins
would require boilerplate (would it)

3) serious generalisation: arbitrary monad transformers. let the user plug and play
whatever semantics they want. upside: ridiculously powerful generalisation. downside:
type hell trying to combine separate monads in separate extensions.



-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings


More information about the Xmonad mailing list