Lisp vs edn #70
YeungOnion
started this conversation in
General
Replies: 1 comment 1 reply
-
In the case of qastle, this was created very specifically as a way of serializing FuncADL queries for use in ServiceX. I'm not familiar with edn, so it's certainly possible that it would have worked for this purpose. I'm not sure how much work it would have saved, since we'd still have needed to write the code to turn FuncADL ASTs into this format and vice versa. If you're interested in the needs of declarative interfaces in HEP in general, you might be interested in the slides from this Analysis Description Languages workshop from 2019 or this HEP queries paper that I collaborated on. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
an intro
Hello,
I'm wanting to contribute in moving particle physics analysis to software engineering at some of the most demanding scales. Declared queries of structured data is a way to express cutflows and I think it's a great way forward and an area I'd like to contribute to.
actual discussion
I'm hoping to understand some of the background for the design of this declarative language query spec. I think lisp s-expressions are quite lean as well, but there is a spec for edn with parsers as well which are leaner as the notion of attributes as parent nodes of attributes are builtin.
Would someone be able to share some of the background about what needs HEP had that were novel and motivated a new spec?
Beta Was this translation helpful? Give feedback.
All reactions