| /dports/lang/racket-minimal/racket-8.3/src/expander/compile/ |
| H A D | side-effect.rkt | 123 (and (or (and (or (and (known-struct-op? d)
225 ;; All properties must be distinct
256 … (lambda (v) (known-good-struct-properties? v immutables-expr super-expr defns))
266 (known-struct-op? o)
267 (eq? 'struct-type (known-struct-op-type o))))))
300 (define (known-good-struct-properties? v immutables-expr super-expr defns)
309 (known-good-struct-property+value? (list-ref prop+val 1)
314 ;; All properties must be distinct
319 (define (known-good-struct-property+value? prop-expr val-expr immutables-expr super-expr defns)
410 (and (known-struct-op? a)
[all …]
|
| /dports/lang/racket/racket-8.3/src/expander/compile/ |
| H A D | side-effect.rkt | 123 (and (or (and (or (and (known-struct-op? d)
225 ;; All properties must be distinct
256 … (lambda (v) (known-good-struct-properties? v immutables-expr super-expr defns))
266 (known-struct-op? o)
267 (eq? 'struct-type (known-struct-op-type o))))))
300 (define (known-good-struct-properties? v immutables-expr super-expr defns)
309 (known-good-struct-property+value? (list-ref prop+val 1)
314 ;; All properties must be distinct
319 (define (known-good-struct-property+value? prop-expr val-expr immutables-expr super-expr defns)
410 (and (known-struct-op? a)
[all …]
|
| /dports/multimedia/pipewire/pipewire-0.3.43/doc/ |
| H A D | spa-pod.dox | 6 A POD can express nested structures of Objects (with properties), Vectors,
41 - `SPA_TYPE_Object`: an object with properties
138 Next we can push some properties in the object:
148 and then the associated value. For performance reasons it is a good
219 // audio/raw properties
250 // audio/raw properties
302 To iterate over the properties in an object you can do:
306 struct spa_pod_object *obj = (struct spa_pod_object*)pod;
328 If the fields in a struct are known, it is much easier to use the
329 parser. Similarly, if the object type (and thus its keys) are known,
[all …]
|
| /dports/www/cadaver/cadaver-0.23.3/ |
| H A D | TODO | 24 DAV refres. 'alias' might be good, since it is like Apache's Alias
52 style... allow different properties to be displayed.
59 - properties: display all... display from namespace
75 - Maybe put a union in struct command to get better typesafeness...
111 - could also interpret known status-codes with more friendly responses.
126 ** Misfeatures (a.k.a. known bugs) **
128 - See INTEROP for known interoperability problems
|
| /dports/math/prng/prng-3.0.2/doc/ |
| H A D | prng.info | 211 (`struct prng *').
220 struct prng *g;
457 - Strong non-linear properties. (e.g. no lattice)
470 suggestions are known.
490 - Strong non-linear properties. (e.g. no lattice)
528 - Strong linear properties.
564 L'Ecuyer, P., Blouin, F. and Couture R. "A search for good
606 No table of good parameters has been published.
690 - Strong non-linear properties.
782 - Generally speaking, most properties of PRNG are preserved
[all …]
|
| /dports/lang/spidermonkey60/firefox-60.9.0/third_party/rust/chrono/ |
| H A D | README.md | 9 Date and time handling for Rust. (also known as `rust-chrono`)
18 There were several previous attempts to bring a good date and time library to Rust,
58 [**`Duration`**](https://lifthrasiir.github.io/rust-chrono/chrono/struct.Duration.html)
61 [`time::Duration`](https://doc.rust-lang.org/time/time/struct.Duration.html) type, but is
67 [**`DateTime`**](https://lifthrasiir.github.io/rust-chrono/chrono/datetime/struct.DateTime.html)
72 [`time::SystemTime`](https://doc.rust-lang.org/std/time/struct.SystemTime.html),
74 [`time::Instant`](https://doc.rust-lang.org/std/time/struct.Instant.html), which
80 There are three well-known `TimeZone` implementations:
138 Various properties are available to the date and time, and can be altered individually.
186 for well-known formats.
[all …]
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/arm64/ |
| H A D | arm-acpi.rst | 19 specifications, then ACPI may not be a good fit for the hardware.
34 reasoning behind ACPI on ARMv8 servers. Actually, we snitch a good portion
81 integrated devices, but there are no good processes for supporting what the
241 above are known as "bindings"; in ACPI, these are known as "Device Properties"
247 properties. For example, device properties could use an ASL construct
401 static int device_probe_dt(struct platform_device *pdev)
407 static int device_probe_acpi(struct platform_device *pdev)
413 static int device_probe(struct platform_device *pdev)
416 struct device_node node = pdev->dev.of_node;
434 static struct of_device_id virtio_mmio_match[] = {
[all …]
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/arm64/ |
| H A D | arm-acpi.rst | 19 specifications, then ACPI may not be a good fit for the hardware.
34 reasoning behind ACPI on ARMv8 servers. Actually, we snitch a good portion
81 integrated devices, but there are no good processes for supporting what the
241 above are known as "bindings"; in ACPI, these are known as "Device Properties"
247 properties. For example, device properties could use an ASL construct
401 static int device_probe_dt(struct platform_device *pdev)
407 static int device_probe_acpi(struct platform_device *pdev)
413 static int device_probe(struct platform_device *pdev)
416 struct device_node node = pdev->dev.of_node;
434 static struct of_device_id virtio_mmio_match[] = {
[all …]
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/arm64/ |
| H A D | arm-acpi.rst | 19 specifications, then ACPI may not be a good fit for the hardware.
34 reasoning behind ACPI on ARMv8 servers. Actually, we snitch a good portion
81 integrated devices, but there are no good processes for supporting what the
241 above are known as "bindings"; in ACPI, these are known as "Device Properties"
247 properties. For example, device properties could use an ASL construct
401 static int device_probe_dt(struct platform_device *pdev)
407 static int device_probe_acpi(struct platform_device *pdev)
413 static int device_probe(struct platform_device *pdev)
416 struct device_node node = pdev->dev.of_node;
434 static struct of_device_id virtio_mmio_match[] = {
[all …]
|
| /dports/multimedia/libv4l/linux-5.13-rc2/Documentation/power/ |
| H A D | power_supply_class.rst | 8 properties to user-space.
32 Attributes/properties
57 Attributes/properties detailed
91 'unknown', if the status is not known).
220 time. Batteries are good example. So, batteries usually care if they're
227 "supplied_to" struct member, and each power_supply_changed() call
239 Properties in struct power_supply_battery_info and their counterparts in the
241 for naming consistency between sysfs attributes and battery node properties.
277 Most likely, no. This class is designed to export properties which are
280 Inferring not available properties using some heuristics or mathematical
|
| /dports/multimedia/v4l-utils/linux-5.13-rc2/Documentation/power/ |
| H A D | power_supply_class.rst | 8 properties to user-space.
32 Attributes/properties
57 Attributes/properties detailed
91 'unknown', if the status is not known).
220 time. Batteries are good example. So, batteries usually care if they're
227 "supplied_to" struct member, and each power_supply_changed() call
239 Properties in struct power_supply_battery_info and their counterparts in the
241 for naming consistency between sysfs attributes and battery node properties.
277 Most likely, no. This class is designed to export properties which are
280 Inferring not available properties using some heuristics or mathematical
|
| /dports/multimedia/v4l_compat/linux-5.13-rc2/Documentation/power/ |
| H A D | power_supply_class.rst | 8 properties to user-space.
32 Attributes/properties
57 Attributes/properties detailed
91 'unknown', if the status is not known).
220 time. Batteries are good example. So, batteries usually care if they're
227 "supplied_to" struct member, and each power_supply_changed() call
239 Properties in struct power_supply_battery_info and their counterparts in the
241 for naming consistency between sysfs attributes and battery node properties.
277 Most likely, no. This class is designed to export properties which are
280 Inferring not available properties using some heuristics or mathematical
|
| /dports/editors/helix/helix-0.5.0/cargo-crates/quickcheck-1.0.3/ |
| H A D | README.md | 179 ### Discarding test results (or, properties are polymorphic!)
267 type](https://docs.rs/quickcheck/*/quickcheck/struct.TestResult.html).
346 One approach is to run your quickcheck properties in a loop that
365 properties with `qc_`. You could leave off the filter, but then
374 Another approach is to just ask quickcheck to run properties more
396 example, where the struct `Point` is defined:
399 struct Point {
406 the trait `Arbitrary` for the struct `Point`:
428 not known to be prime while building the sieve) and slots marked with `true`
429 are known to not be prime. For each `n`, all of its multiples in this array
[all …]
|
| /dports/security/arti/arti-9d0ede26801cdb182daa85c3eb5f0058dc178eb6/cargo-crates/quickcheck-1.0.3/ |
| H A D | README.md | 179 ### Discarding test results (or, properties are polymorphic!)
267 type](https://docs.rs/quickcheck/*/quickcheck/struct.TestResult.html).
346 One approach is to run your quickcheck properties in a loop that
365 properties with `qc_`. You could leave off the filter, but then
374 Another approach is to just ask quickcheck to run properties more
396 example, where the struct `Point` is defined:
399 struct Point {
406 the trait `Arbitrary` for the struct `Point`:
428 not known to be prime while building the sieve) and slots marked with `true`
429 are known to not be prime. For each `n`, all of its multiples in this array
[all …]
|
| /dports/security/sequoia/sequoia-383133f6be990237044900a4df676488bf8dd71e/cargo-crates/quickcheck-0.9.2/ |
| H A D | README.md | 168 ### Discarding test results (or, properties are polymorphic!)
256 type](https://docs.rs/quickcheck/*/quickcheck/struct.TestResult.html).
335 One approach is to run your quickcheck properties in a loop that
354 properties with `qc_`. You could leave off the filter, but then
363 Another approach is to just ask quickcheck to run properties more
385 example, where the struct `Point` is defined:
388 struct Point {
395 the trait `Arbitrary` for the struct `Point`:
417 not known to be prime while building the sieve) and slots marked with `true`
418 are known to not be prime. For each `n`, all of its multiples in this array
[all …]
|
| /dports/multimedia/gstreamer1-plugins-rust/gst-plugins-rs-d0466b3eee114207f851b37cae0015c0e718f021/tutorial/ |
| H A D | tutorial-2.md | 51 // Default values of properties
60 struct Settings {
82 struct State {
102 pub struct SineSrc {
171 // Metadata for the properties
172 fn properties() -> &'static [glib::ParamSpec] {
485 // here, and for good measure also decide that the closest value to 1
486 // channel is good.
821 struct ClockWait {
836 struct SineSrc {
[all …]
|
| /dports/lang/racket/racket-8.3/collects/racket/contract/private/ |
| H A D | guts.rkt | 9 (submod "collapsible-common.rkt" properties)
44 ;; helpers for adding properties that check syntax uses
239 (contract-struct-first-order
243 ((contract-struct-first-order
331 (struct name-default ())
423 (memq x the-known-good-contracts)))])]
446 (define the-known-good-contracts
447 (let-syntax ([m (λ (x) #`(list #,@(known-good-contracts)))])
539 (if (contract-struct? sub) (contract-struct-name sub) sub)))
734 (define-struct regexp/c (reg name)
[all …]
|
| /dports/lang/racket-minimal/racket-8.3/collects/racket/contract/private/ |
| H A D | guts.rkt | 9 (submod "collapsible-common.rkt" properties)
44 ;; helpers for adding properties that check syntax uses
239 (contract-struct-first-order
243 ((contract-struct-first-order
331 (struct name-default ())
423 (memq x the-known-good-contracts)))])]
446 (define the-known-good-contracts
447 (let-syntax ([m (λ (x) #`(list #,@(known-good-contracts)))])
539 (if (contract-struct? sub) (contract-struct-name sub) sub)))
734 (define-struct regexp/c (reg name)
[all …]
|
| /dports/multimedia/librespot/librespot-0.1.3/cargo-crates/chrono-0.4.13/ |
| H A D | README.md | 26 There were several previous attempts to bring a good date and time library to Rust,
73 the [`time::Duration`](https://docs.rs/time/0.1.40/time/struct.Duration.html) type
82 the standard [`Duration`](https://doc.rust-lang.org/std/time/struct.Duration.html) type,
93 [**`DateTime`**](https://docs.rs/chrono/0.4/chrono/struct.DateTime.html)
98 [`time::SystemTime`](https://doc.rust-lang.org/std/time/struct.SystemTime.html),
100 [`time::Instant`](https://doc.rust-lang.org/std/time/struct.Instant.html), which
106 There are three well-known `TimeZone` implementations:
123 ([`Utc::now()`](https://docs.rs/chrono/0.4/chrono/offset/struct.Utc.html#method.now))
165 Various properties are available to the date and time, and can be altered individually.
221 for well-known formats.
[all …]
|
| /dports/devel/interactive_rebase_tool/git-interactive-rebase-tool-1.2.1/cargo-crates/chrono-0.4.6/ |
| H A D | README.md | 29 There were several previous attempts to bring a good date and time library to Rust,
76 the [`time::Duration`](https://docs.rs/time/0.1.40/time/struct.Duration.html) type
85 the standard [`Duration`](https://docs.rs/time/0.1.40/time/struct.Duration.html) type,
96 [**`DateTime`**](https://docs.rs/chrono/0.4.6/chrono/struct.DateTime.html)
101 [`time::SystemTime`](https://doc.rust-lang.org/std/time/struct.SystemTime.html),
103 [`time::Instant`](https://doc.rust-lang.org/std/time/struct.Instant.html), which
109 There are three well-known `TimeZone` implementations:
126 ([`Utc::now()`](https://docs.rs/chrono/0.4.6/chrono/offset/struct.Utc.html#method.now))
168 Various properties are available to the date and time, and can be altered individually.
222 for well-known formats.
[all …]
|
| /dports/games/jaggedalliance2/ja2-stracciatella-0.18.0/cargo-crates/chrono-0.4.15/ |
| H A D | README.md | 26 There were several previous attempts to bring a good date and time library to Rust,
81 the [`time::Duration`](https://docs.rs/time/0.1.40/time/struct.Duration.html) type
101 [**`DateTime`**](https://docs.rs/chrono/0.4/chrono/struct.DateTime.html)
106 [`time::SystemTime`](https://doc.rust-lang.org/std/time/struct.SystemTime.html),
108 [`time::Instant`](https://doc.rust-lang.org/std/time/struct.Instant.html), which
114 There are three well-known `TimeZone` implementations:
131 ([`Utc::now()`](https://docs.rs/chrono/0.4/chrono/offset/struct.Utc.html#method.now))
173 Various properties are available to the date and time, and can be altered individually.
229 for well-known formats.
276 are similar but for well-known formats.
[all …]
|
| /dports/games/genact/genact-0.10.0/cargo-crates/chrono-0.4.15/ |
| H A D | README.md | 26 There were several previous attempts to bring a good date and time library to Rust,
81 the [`time::Duration`](https://docs.rs/time/0.1.40/time/struct.Duration.html) type
101 [**`DateTime`**](https://docs.rs/chrono/0.4/chrono/struct.DateTime.html)
106 [`time::SystemTime`](https://doc.rust-lang.org/std/time/struct.SystemTime.html),
108 [`time::Instant`](https://doc.rust-lang.org/std/time/struct.Instant.html), which
114 There are three well-known `TimeZone` implementations:
131 ([`Utc::now()`](https://docs.rs/chrono/0.4/chrono/offset/struct.Utc.html#method.now))
173 Various properties are available to the date and time, and can be altered individually.
229 for well-known formats.
276 are similar but for well-known formats.
[all …]
|
| /dports/accessibility/sctd/sctd-0.2.0/cargo-crates/chrono-0.4.11/ |
| H A D | README.md | 29 There were several previous attempts to bring a good date and time library to Rust,
76 the [`time::Duration`](https://docs.rs/time/0.1.40/time/struct.Duration.html) type
85 the standard [`Duration`](https://doc.rust-lang.org/std/time/struct.Duration.html) type,
96 [**`DateTime`**](https://docs.rs/chrono/0.4/chrono/struct.DateTime.html)
101 [`time::SystemTime`](https://doc.rust-lang.org/std/time/struct.SystemTime.html),
103 [`time::Instant`](https://doc.rust-lang.org/std/time/struct.Instant.html), which
109 There are three well-known `TimeZone` implementations:
126 ([`Utc::now()`](https://docs.rs/chrono/0.4/chrono/offset/struct.Utc.html#method.now))
168 Various properties are available to the date and time, and can be altered individually.
224 for well-known formats.
[all …]
|
| /dports/sysutils/vector/vector-0.10.0/cargo-crates/chrono-0.4.11/ |
| H A D | README.md | 29 There were several previous attempts to bring a good date and time library to Rust,
76 the [`time::Duration`](https://docs.rs/time/0.1.40/time/struct.Duration.html) type
85 the standard [`Duration`](https://doc.rust-lang.org/std/time/struct.Duration.html) type,
96 [**`DateTime`**](https://docs.rs/chrono/0.4/chrono/struct.DateTime.html)
101 [`time::SystemTime`](https://doc.rust-lang.org/std/time/struct.SystemTime.html),
103 [`time::Instant`](https://doc.rust-lang.org/std/time/struct.Instant.html), which
109 There are three well-known `TimeZone` implementations:
126 ([`Utc::now()`](https://docs.rs/chrono/0.4/chrono/offset/struct.Utc.html#method.now))
168 Various properties are available to the date and time, and can be altered individually.
224 for well-known formats.
[all …]
|
| /dports/security/sequoia/sequoia-383133f6be990237044900a4df676488bf8dd71e/cargo-crates/chrono-0.4.15/ |
| H A D | README.md | 26 There were several previous attempts to bring a good date and time library to Rust,
81 the [`time::Duration`](https://docs.rs/time/0.1.40/time/struct.Duration.html) type
101 [**`DateTime`**](https://docs.rs/chrono/0.4/chrono/struct.DateTime.html)
106 [`time::SystemTime`](https://doc.rust-lang.org/std/time/struct.SystemTime.html),
108 [`time::Instant`](https://doc.rust-lang.org/std/time/struct.Instant.html), which
114 There are three well-known `TimeZone` implementations:
131 ([`Utc::now()`](https://docs.rs/chrono/0.4/chrono/offset/struct.Utc.html#method.now))
173 Various properties are available to the date and time, and can be altered individually.
229 for well-known formats.
276 are similar but for well-known formats.
[all …]
|