Skip to content
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

Making ObType a separate crate #1339

Open
samuelcolvin opened this issue Jun 24, 2024 · 1 comment
Open

Making ObType a separate crate #1339

samuelcolvin opened this issue Jun 24, 2024 · 1 comment
Labels

Comments

@samuelcolvin
Copy link
Member

See samuelcolvin/rtoml#59.

We should move ObType to a separate crate so it can be reused by other projects, there's also a chance that it allows one of us, or something else to come along and make it faster.

pub enum ObType {
None,
// numeric types
Int,
IntSubclass,
Bool,
Float,
FloatSubclass,
Decimal,
// string types
Str,
StrSubclass,
Bytes,
Bytearray,
// sequence types
List,
Tuple,
Set,
Frozenset,
// mapping types
Dict,
// datetime types
Datetime,
Date,
Time,
Timedelta,
// types from this package
Url,
MultiHostUrl,
// anything with __pydantic_serializer__, including BaseModel and pydantic dataclasses
PydanticSerializable,
// vanilla dataclasses
Dataclass,
// enum type
Enum,
// generator type
Generator,
// Path
Path,
//Pattern,
Pattern,
// Uuid
Uuid,
// unknown type
Unknown,
}

@sydney-runkle
Copy link
Member

This would probably be a good issue for me to pick up at some point in terms of comfort with the rust ecosystem 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants