1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
// SPDX-FileCopyrightText: 2025 Daniel Vrátil <me@dvratil.cz>
//
// SPDX-License-Identifier: MIT
// This file will be populated by prost-build in build.rs
// Include the generated Protobuf code.
// The actual filenames will be based on your .proto package structure.
// For example, if your aggregator.proto has `package google.protos.zetasketch;`
// the generated module will likely be `google.protos.zetasketch`.
// Assuming the proto files `aggregator.proto` and `hllplus_unique.proto`
// declare a package like `com.google.protos.zetasketch` or similar.
// The include path will depend on the package name in the .proto files.
// If they are in `google.protos.zetasketch`:
// pub mod google {
// pub mod protos {
// pub mod zetasketch {
// include!(concat!(env!("OUT_DIR"), "/google.protos.zetasketch.rs"));
// }
// }
// }
// For now, let's assume a simpler structure or that the user will adjust this.
// If the .proto files define `package zetasketch;`, it would be:
// pub mod zetasketch {
// include!(concat!(env!("OUT_DIR"), "/zetasketch.rs"));
// }
// Placeholder for the actual generated code include.
// The user will need to ensure proto files are copied and build.rs runs successfully.
// The generated file will be in OUT_DIR, and we're telling build.rs to put it in `src/protos`.
// So, we'll reference it from there.
// This assumes that aggregator.proto and hllplus_unique.proto might generate
// separate .rs files or a combined one based on their package definitions.
// Let's assume a common package `zetasketch_protos` for simplicity of the generated file name.
// The `build.rs` is configured with `out_dir("src/protos")`.
// Assuming the .proto files use `package com.google.protos.zetasketch;`
// This will generate a single `com.google.protos.zetasketch.rs` file.
// To silence clippy warnings from generated code
pub use Id as DefaultOpsTypeId;
pub use AggregatorStateProto;
pub use AggregatorStatsProto;
pub use AggregatorType;
pub use AggregatorValueStatsProto;
pub use DefaultOpsType;
pub use Id as CustomValueTypeId;
pub use CustomValueType;
pub use HyperLogLogPlusUniqueStateProto;