-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've been considering adding lexical lookup to s-format #27
Comments
I think that looks brilliant. But maybe as a separate function, so you can ditch the 'lex-value all together?
|
The only trouble with that is that I think there are two things that I'm using this code right now:
So I can go:
or I could use lex-val. I guess I could start adding more dynamic options to format to control |
What I want are fewer dynamic options and instead a cleaner API. Functions On Mon, Apr 29, 2013 at 3:32 PM, Nic Ferrier notifications@github.comwrote:
|
Do you? I like all that being able to change the behaviour of things by let binding and such. It's fun. |
How about this:
My only concern with this is that often you want the lex value to be lisp printed ("%S" instead of "%s") and that's not possible here. It could be done with a switch or a dyn var. |
It's too convoluted for me. I would be a happy man if I could just have a formatting function that grabs content off the current scope. But come to think of it, maybe that's just |
For all the reasons that s-format is better. My use case is this:
Code that with concat and see how happy you are :-) |
Haha, you're right. That would be terrible. :-) On Mon, Apr 29, 2013 at 11:18 PM, Nic Ferrier notifications@github.comwrote:
|
It seems like a standard templating problem to me. And I've never really got how we can fix that with simple Lisp. Maybe there is a better solution but I'm not aware of it. |
So you can do this:
Good idea? Bad idea?
The text was updated successfully, but these errors were encountered: