Skip to content
This repository was archived by the owner on May 16, 2023. It is now read-only.

Use Rust as the source of truth / break with the Go SDK #30

Closed
LegNeato opened this issue Jan 5, 2021 · 2 comments · Fixed by #133
Closed

Use Rust as the source of truth / break with the Go SDK #30

LegNeato opened this issue Jan 5, 2021 · 2 comments · Fixed by #133
Labels
enhancement New feature or request question Further information is requested

Comments

@LegNeato
Copy link
Contributor

LegNeato commented Jan 5, 2021

Eventually we'll probably want to have Rust as the source of truth rather than generating from Go.

  • Rust's type system is more expressive and can be more correct and ergonomic than what we can infer from Go.
  • There are not many maintainers of the Go code so we will always lag behind / wait on them.

We would only want to break with the codegen when we have a critical mass of people using this lib and willing to provide event defs directly in Rust. I don't think we are there but wanted to open this so people can tell me when we are 😄 .

@LegNeato LegNeato added enhancement New feature or request question Further information is requested labels Jan 5, 2021
@LegNeato
Copy link
Contributor Author

@calavera what do you think about this? I feel like most bugs these days are because Go's type system is less expressive and/or they have a bug in their defs.

@calavera
Copy link
Owner

calavera commented Jan 24, 2022

This is probably the best path forward. #50 is a good example of people providing hand written events. I think the only events I miss so far in this crate are DynamoDB events, and we cannot even generate them from the Go structs anyways.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants