-
Notifications
You must be signed in to change notification settings - Fork 35
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
[format] bugs #2205
Comments
I also don;t like the cyclone idea that you can bang secondary inlets and use lists to spread elements I may have this in other objects I stole from cyclone and I should reconsider it all |
pack2 comes to mind |
um format float sai como float e pode ser, sei lá, passar por algum processo de arredondamento com o campo de precisão e ser truncado ao convertido a um 'int', mas isso faz sentido? Queremos essa funcionalidade? sei lá, talvez sim, mantém que uma porra dessa é um float e tal, e, enfim, pode ser melhor documentado isso mas continua a ideia de adicionar o seletor 'symbol' e 'list' e tirar as outras frescuras da cyclone |
maybe just output fucking symbols, no lists!!!
it blows up if I use flags in the wrong order as in cyclone (e.g. "%.3#g"), but if I use in the correct order (e.g. %#.3g) it's not working... maybe related to the bug below
symbols with spaces get split (same with sprintf)
I'd expect a symbol output always... maybe consider adding the symbol/list selectors always and use a -trim flag
The text was updated successfully, but these errors were encountered: