7:50:29axionThe problem is I want to inform the DECLAIM of the type of the keyword arguments in the form they are expected in such as: &key (:min single-float) (:max single-float)
7:50:41axionI cannot adapt my naive extraction function to do that
7:51:47Bikethis is supposed to mean that the argument is called out-vec, the key arg is :out-vec, the default value is 1, and it's typed as an "axvec"?
7:52:39axionIt's an example...do not look at it as real code :)
7:52:56Bikei just want to know that i understand your desired syntax
7:53:05Bikewell, if i was you i'd use the lambda list parser in alexandria
13:21:57beachAny particular reason you are using structure classes rather than standard classes?
13:24:10ogamitaNotice that there are macros that allows you to define classes using the same syntax as defstruct, if that's the reason.
13:26:23axionbeach: I have been over this a few times here. It's to have typed structs, that compile down to arrays except with named slots for accessing elements.
13:28:08Xachthat is more a description of the effect than the reason
13:29:39axionand also for code that is quite a few years old that is a beast to maintain, but it is the result of a friend and I disassembling a ton to write an efficient linear algebra library.
14:08:27ogamitaaxion: so (defstruct (example (:type vector)) …)
14:09:25ogamitaaxion: normally, changing the defstruct option (or s/defstruct/define-structure/ to get CLOS classes) will left the other program properties invariants and can be done rather easily.
14:10:03ogamita(Unless you're doing type punning, for performance reasons).
16:31:27beachI just created two more (very small) tasks on the Lisp Guild site: https://github.com/Lisp-Guild/lisp-todo/projects/1
16:40:29Reinischsorry, I've been slacking. I'll get back on the horse soon!