11#![ deny( warnings) ]
22// Allow non upper case globals from C
33#![ allow( non_upper_case_globals) ]
4+ #![ allow( incomplete_features) ]
5+ #![ feature( adt_const_params) ]
46
57mod c_oracle_header;
68mod deserialize;
@@ -17,24 +19,25 @@ mod tests;
1719#[ cfg( feature = "debug" ) ]
1820mod log;
1921
20- use crate :: error:: OracleError ;
21- use processor:: process_instruction;
22-
23- use solana_program:: entrypoint;
24-
25- //Below is a high lever description of the rust/c setup.
26-
27- //As we migrate from C to Rust, our Rust code needs to be able to interact with C
28- //build-bpf.sh is set up to compile the C code into a two archive files
29- //contained in `./program/c/target/`
30- // - `libcpyth-bpf.a` contains the bpf version for production code
31- // - `libcpyth-native.a` contains the systems architecture version for tests
32-
33- //We also generate bindings for the types and constants in oracle.h (as well as other things
34- //included in bindings.h), these bindings can be accessed through c_oracle_header.rs
35- //Bindings allow us to access type definitions, function definitions and constants. In order to
36- //add traits to the bindings, we use the parser in build.rs. The traits must be defined/included
37- //at the the top of c_oracle_headers.rs. One of the most important traits we deal are the Borsh
38- //serialization traits.
22+ use {
23+ crate :: error:: OracleError ,
24+ processor:: process_instruction,
25+ solana_program:: entrypoint,
26+ } ;
27+
28+ // Below is a high lever description of the rust/c setup.
29+
30+ // As we migrate from C to Rust, our Rust code needs to be able to interact with C
31+ // build-bpf.sh is set up to compile the C code into a two archive files
32+ // contained in `./program/c/target/`
33+ // - `libcpyth-bpf.a` contains the bpf version for production code
34+ // - `libcpyth-native.a` contains the systems architecture version for tests
35+
36+ // We also generate bindings for the types and constants in oracle.h (as well as other things
37+ // included in bindings.h), these bindings can be accessed through c_oracle_header.rs
38+ // Bindings allow us to access type definitions, function definitions and constants. In order to
39+ // add traits to the bindings, we use the parser in build.rs. The traits must be defined/included
40+ // at the the top of c_oracle_headers.rs. One of the most important traits we deal are the Borsh
41+ // serialization traits.
3942
4043entrypoint ! ( process_instruction) ;
0 commit comments