Crates.io | flowcore |
lib.rs | flowcore |
version | 0.142.0 |
source | src |
created_at | 2021-04-03 16:10:11.462845 |
updated_at | 2023-09-28 17:34:19.139828 |
description | Structures shared between runtime and clients |
homepage | http://andrewdavidmackenzie.github.io/flow/ |
repository | https://github.com/andrewdavidmackenzie/flow/ |
max_upload_size | |
id | 378365 |
size | 261,346 |
flowcore
flowcore
is a library of structs and traits related to flow
that are shared between multiple
crates in the flow
project.
Implementation
traitThis is a trait that implementations of flow 'functions' must implement in order for them to be invoked by the flowrlib (or other) run-time library.
An example of a function implementing the Implementation
trait can be found in docs.rs for
Implementation
Provider
This implements a content provider
that resolves URLs and then gets the content of the url.
flowcore
crate supports a number of "features" for conditional compiling with more or less features.
These are the conditionally compiled features of flowcore
:
Examples
flowrlib
library crate compiles flowcore
activating the "file_provider", "http_provider",
"context" and "meta_provider" featuresflowr
compiled flowcore
activating the "context" feature as it provides context functions
. It has a
number of features that, if activated, active corresponding features in flowcore
(flowr
"debugger"
feature actives "flowcore/debugger" feature.) and it depends on flowrlib
(above) that in turn activates
featuresflowrex
compiles flowcore
with the default set of features (which is the minimal set in the case
of flowcore
as it does not provide ant context functions
("context" feature), nor does it coordinate flow
running and provide a debugger ("debugger" feature), nor does it have the need for running "online_tests",
and lastly it does not fetch content via any of the various "providers" ("meta_provider", "file_provider",
and "http_provider" features).