anki/rs/ankirs/Cargo.toml

[package]
name = "ankirs"
version = "0.1.0"
edition = "2018"
authors = ["Ankitects Pty Ltd and contributors"]

[dependencies]
nom = "5.0.1"
failure = "0.1.6"
prost = "0.5.0"
bytes = "0.4"
chrono = "0.4.10"

[build-dependencies]
prost-build = "0.5.0"
split the rust code into a workspace 2019-12-23 05:42:14 +01:00			`[package]`
			`name = "ankirs"`
			`version = "0.1.0"`
			`edition = "2018"`
			`authors = ["Ankitects Pty Ltd and contributors"]`
use protobuf for python/rust bridge If we go ahead with betterproto on the Python side, it will mean bumping the minimum Python dependency to 3.7. 2019-12-24 04:33:44 +01:00
			`[dependencies]`
compute template requirements in Rust on a 100 field template, what took ~75 seconds now takes ~3 seconds. 2019-12-24 05:05:15 +01:00			`nom = "5.0.1"`
use protobuf for python/rust bridge If we go ahead with betterproto on the Python side, it will mean bumping the minimum Python dependency to 3.7. 2019-12-24 04:33:44 +01:00			`failure = "0.1.6"`
			`prost = "0.5.0"`
			`bytes = "0.4"`
rework the new scheduler's rollover/day counting code The previous implementation interpreted the creation date as a local time, and applied the rollover to that. If the initial creation date was around midnight local time, even a one hour change due to daylight savings could result in Anki skipping or doubling up on a day. To address this, the rollover is now applied to the current time instead of the creation date. The new code needs the current time passed into it. This makes it easier to unit test, and for AnkiWeb to be able to use the user's local timezone. The new timezone code is currently disabled, as this code needs to be ported to all clients before it can be activated. 2019-12-27 09:14:19 +01:00			`chrono = "0.4.10"`
use protobuf for python/rust bridge If we go ahead with betterproto on the Python side, it will mean bumping the minimum Python dependency to 3.7. 2019-12-24 04:33:44 +01:00
			`[build-dependencies]`
			`prost-build = "0.5.0"`