├── .github └── workflows │ └── rust.yml ├── .gitignore ├── CONTRIBUTING.md ├── Cargo.toml ├── LICENSE-APACHE ├── LICENSE-MIT ├── README.md ├── changelog.md ├── src ├── lib.rs └── streams.rs └── tests ├── connector.rs └── macros.rs /.github/workflows/rust.yml: -------------------------------------------------------------------------------- 1 | name: Rust 2 | 3 | on: 4 | push: 5 | branches: [ master ] 6 | pull_request: 7 | branches: [ master ] 8 | 9 | jobs: 10 | build-lint-test-benchmark: 11 | 12 | runs-on: ubuntu-latest 13 | 14 | steps: 15 | - uses: actions/checkout@v2 16 | - name: Build 17 | run: cargo build --verbose 18 | - name: clippy 19 | run: cargo clippy 20 | - name: fmt 21 | run: cargo fmt --all -- --check 22 | - name: test 23 | run: cargo test 24 | - name: doc 25 | run: cargo doc 26 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | target 2 | Cargo.lock 3 | *.sublime-workspace 4 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | ## Issues 2 | 3 | All issues, may it be feature requests, or bugs, are treated as **problems**. 4 | In any case it is important to be able to reproduce or understand it. To help in doing so, please state the following information: 5 | 6 | * a description of the problem 7 | * steps to reproduce the problem (if applicable) 8 | * library version showing the problem (if applicable) 9 | 10 | The emphasis on the term **problem** originates from the observed tendency of issues being more like a solution to a problem, 11 | which is not stated in detail, making good solutions more difficult to achieve. 12 | 13 | ## Pull Requests 14 | 15 | Feel free to make any kind of Pull Request - all contributions are welcome. 16 | 17 | The only thing to keep in mind is the commit message format, which is described below. 18 | 19 | ### Commit Message Format 20 | 21 | The format is taken directly from [angular.js][angular-contribution-guide], as is this text. 22 | 23 | Each commit message consists of a **header**, a **body** and a **footer**. The header has a special 24 | format that includes a **type**, a **scope** and a **subject**: 25 | 26 | ``` 27 | (): 28 | 29 | 30 | 31 |