minus-squareasperan@programming.devOPtoRust@programming.dev•declarative-env 0.1.0 releasedlinkfedilinkarrow-up1·4 days ago If the spec contains default values why not make a constructor with all the missing fields or implement Default when all fields are covered? For the first implementation I wanted to keep it simple, I don’t exclude that in the future it will change. Also lol: Yep, I still need to figure out deep macro testing, for now I use the integration tests and cargo expand. This will absolutely change in the future :) Thanks for the feedback! linkfedilink
asperan@programming.dev to Opensource@programming.devEnglish · edit-25 days agodeclarative-env 0.1.0 releasedplus-squarecrates.ioexternal-linkmessage-square0fedilinkarrow-up16arrow-down10
arrow-up16arrow-down1external-linkdeclarative-env 0.1.0 releasedplus-squarecrates.ioasperan@programming.dev to Opensource@programming.devEnglish · edit-25 days agomessage-square0fedilink
asperan@programming.dev to Rust@programming.devEnglish · 5 days agodeclarative-env 0.1.0 releasedplus-squarecrates.ioexternal-linkmessage-square2fedilinkarrow-up16arrow-down10
arrow-up16arrow-down1external-linkdeclarative-env 0.1.0 releasedplus-squarecrates.ioasperan@programming.dev to Rust@programming.devEnglish · 5 days agomessage-square2fedilink
minus-squareasperan@programming.devtoProgrammer Humor@programming.dev•Stringly typedlinkfedilinkarrow-up23·6 days agoIt is also the bash approach, isn’t it?! linkfedilink
For the first implementation I wanted to keep it simple, I don’t exclude that in the future it will change.
Yep, I still need to figure out deep macro testing, for now I use the integration tests and cargo expand. This will absolutely change in the future :)
Thanks for the feedback!