| /dports/lang/racket/racket-8.3/src/expander/syntax/ |
| H A D | serialize.rkt | 3 "../syntax/syntax.rkt"
12 (struct serialized-syntax (version mpis base-mpi-pos data need-registry?)
38 (serialized-syntax (version)
46 (unless (serialized-syntax? data)
48 (unless (equal? (version) (serialized-syntax-version data))
52 "found" (serialized-syntax-version data)))
56 (define orig-mpis (deserialize-module-path-index-data (serialized-syntax-mpis data)))
58 (let ([pos (serialized-syntax-base-mpi-pos data)])
66 (define bulk-binding-registry (and (serialized-syntax-need-registry? data)
67 (namespace-bulk-binding-registry (current-namespace))))
[all …]
|
| /dports/lang/racket-minimal/racket-8.3/src/expander/syntax/ |
| H A D | serialize.rkt | 3 "../syntax/syntax.rkt"
12 (struct serialized-syntax (version mpis base-mpi-pos data need-registry?)
38 (serialized-syntax (version)
46 (unless (serialized-syntax? data)
48 (unless (equal? (version) (serialized-syntax-version data))
52 "found" (serialized-syntax-version data)))
56 (define orig-mpis (deserialize-module-path-index-data (serialized-syntax-mpis data)))
58 (let ([pos (serialized-syntax-base-mpi-pos data)])
66 (define bulk-binding-registry (and (serialized-syntax-need-registry? data)
67 (namespace-bulk-binding-registry (current-namespace))))
[all …]
|
| /dports/lang/racket-minimal/racket-8.3/src/expander/compile/ |
| H A D | serialize.rkt | 7 "../syntax/syntax.rkt"
30 ;; Module path indexes are serialized to code that runs to reconstruct
32 ;; serialized to somewhat expression-shaped data and interpreted for
36 ;; To support sharing and cycles, serialized data is represented by:
312 ;; no need to find sharing
367 ;; for unmarshaling, we need to map it to ka new step number
385 ;; Accumulate the serialized stream:
655 ,(if syntax-support? bulk-binding-registry-id #f)
770 [(#:bulk-binding-registry) (values bulk-binding-registry (add1 pos))]
771 [(#:syntax)
[all …]
|
| /dports/lang/racket/racket-8.3/src/expander/compile/ |
| H A D | serialize.rkt | 7 "../syntax/syntax.rkt"
30 ;; Module path indexes are serialized to code that runs to reconstruct
32 ;; serialized to somewhat expression-shaped data and interpreted for
36 ;; To support sharing and cycles, serialized data is represented by:
312 ;; no need to find sharing
367 ;; for unmarshaling, we need to map it to ka new step number
385 ;; Accumulate the serialized stream:
655 ,(if syntax-support? bulk-binding-registry-id #f)
770 [(#:bulk-binding-registry) (values bulk-binding-registry (add1 pos))]
771 [(#:syntax)
[all …]
|
| /dports/lang/racket-minimal/racket-8.3/src/expander/eval/ |
| H A D | module.rkt | 108 ;; `c`, which could cause the serialized form of syntax objects to
153 (lambda (bulk-binding-registry)
154 ;; Avoids a leak of some namespace's bulk-binding registry into the
158 … (force-syntax-deserialize syntax-literals-data-instance bulk-binding-registry))
160 (lambda (data-box ns phase-shift self bulk-binding-registry insp)
263 phase-shift original-self self bulk-binding-registry insp
266 (force-syntax-deserialize syntax-literals-data-instance bulk-binding-registry))
274 #:bulk-binding-registry bulk-binding-registry
311 (define (force-syntax-deserialize syntax-literals-data-instance bulk-binding-registry)
316 ;; We need to make sure there's something to deserialize; if it's already done
[all …]
|
| /dports/lang/racket/racket-8.3/src/expander/eval/ |
| H A D | module.rkt | 108 ;; `c`, which could cause the serialized form of syntax objects to
153 (lambda (bulk-binding-registry)
154 ;; Avoids a leak of some namespace's bulk-binding registry into the
158 … (force-syntax-deserialize syntax-literals-data-instance bulk-binding-registry))
160 (lambda (data-box ns phase-shift self bulk-binding-registry insp)
263 phase-shift original-self self bulk-binding-registry insp
266 (force-syntax-deserialize syntax-literals-data-instance bulk-binding-registry))
274 #:bulk-binding-registry bulk-binding-registry
311 (define (force-syntax-deserialize syntax-literals-data-instance bulk-binding-registry)
316 ;; We need to make sure there's something to deserialize; if it's already done
[all …]
|
| /dports/devel/gitlab-runner/gitlab-runner-8925d9a06fd8e452e2161a768462652a2a13111f/vendor/github.com/docker/distribution/distribution-2.7.0/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| H A D | oauth.md | 4 keywords: registry, on-prem, images, tags, repository, distribution, oauth2, advanced
60 (REQUIRED) String identifying the client. This client_id does not need
63 clients. Accepted syntax is defined in
145 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
184 grant_type=refresh_token&refresh_token=kas9Da81Dfa8&service=registry-1.docker.io&client_id=dockeren…
|
| /dports/sysutils/istio/istio-1.6.7/vendor/github.com/docker/distribution/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| /dports/databases/timescaledb-backup/timescaledb-backup-0.1.1/vendor/github.com/docker/distribution/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| H A D | oauth.md | 4 keywords: registry, on-prem, images, tags, repository, distribution, oauth2, advanced
60 (REQUIRED) String identifying the client. This client_id does not need
63 clients. Accepted syntax is defined in
145 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
184 grant_type=refresh_token&refresh_token=kas9Da81Dfa8&service=registry-1.docker.io&client_id=dockeren…
|
| /dports/net-mgmt/promscale/promscale-0.6.2/vendor/github.com/docker/distribution/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| H A D | oauth.md | 4 keywords: registry, on-prem, images, tags, repository, distribution, oauth2, advanced
60 (REQUIRED) String identifying the client. This client_id does not need
63 clients. Accepted syntax is defined in
145 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
184 grant_type=refresh_token&refresh_token=kas9Da81Dfa8&service=registry-1.docker.io&client_id=dockeren…
|
| /dports/net-mgmt/prometheus2/prometheus-2.30.3/vendor/github.com/docker/distribution/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| H A D | oauth.md | 4 keywords: registry, on-prem, images, tags, repository, distribution, oauth2, advanced
60 (REQUIRED) String identifying the client. This client_id does not need
63 clients. Accepted syntax is defined in
145 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
184 grant_type=refresh_token&refresh_token=kas9Da81Dfa8&service=registry-1.docker.io&client_id=dockeren…
|
| /dports/sysutils/helm/helm-3.5.2/vendor/github.com/docker/distribution/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| H A D | oauth.md | 4 keywords: registry, on-prem, images, tags, repository, distribution, oauth2, advanced
60 (REQUIRED) String identifying the client. This client_id does not need
63 clients. Accepted syntax is defined in
145 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
184 grant_type=refresh_token&refresh_token=kas9Da81Dfa8&service=registry-1.docker.io&client_id=dockeren…
|
| /dports/security/vault/vault-1.8.2/vendor/github.com/docker/distribution/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| H A D | oauth.md | 4 keywords: registry, on-prem, images, tags, repository, distribution, oauth2, advanced
60 (REQUIRED) String identifying the client. This client_id does not need
63 clients. Accepted syntax is defined in
145 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
184 grant_type=refresh_token&refresh_token=kas9Da81Dfa8&service=registry-1.docker.io&client_id=dockeren…
|
| /dports/net-im/dendrite/dendrite-0.5.1/vendor/github.com/docker/distribution/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| H A D | oauth.md | 4 keywords: registry, on-prem, images, tags, repository, distribution, oauth2, advanced
60 (REQUIRED) String identifying the client. This client_id does not need
63 clients. Accepted syntax is defined in
145 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
184 grant_type=refresh_token&refresh_token=kas9Da81Dfa8&service=registry-1.docker.io&client_id=dockeren…
|
| /dports/misc/concourse/concourse-6.7.2/vendor/github.com/docker/distribution/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| /dports/sysutils/docker-registry/distribution-2.7.1/docs/spec/auth/ |
| H A D | token.md | 11 
13 1. Attempt to begin a push/pull operation with the registry.
54 registry.
57 repository `samalba/my-app`. For the registry to authorize this, I will need
64 Docker-Distribution-Api-Version: registry/2.0
83 need to include sufficient access entries in its claim set. To respond to this
84 challenge, the client will need to make a `GET` request to the URL
114 String identifying the client. This client_id does not need
117 clients. Accepted syntax is defined in
168 (Optional) The <a href="https://www.ietf.org/rfc/rfc3339.txt">RFC3339</a>-serialized UTC
[all …]
|
| /dports/www/osrm-backend/osrm-backend-5.26.0/third_party/sol2/docs/source/api/ |
| H A D | table.rst | 14 … a ``std::tuple``, being indexed into using ``[key]`` syntax and setting keys with a similar synta…
51 …returned variable will cause a panic to be fired by the lua C API. If you need to check for keys, …
88 …llables and lambdas are serialized, as there may be issues on GCC-based implementations. See this …
104 …llables and lambdas are serialized, as there may be issues on GCC-based implementations. See this …
117 … Lua to understand that a callable object (such as a lambda) should be serialized as a function an…
214 …llables and lambdas are serialized, as there may be issues on GCC-based implementations. See this …
|
| /dports/textproc/py-markdown/Markdown-3.3.4/docs/extensions/ |
| H A D | api.md | 5 …wn includes an API for extension writers to plug their own custom functionality and syntax into the
409 1. Inline Processors no longer need to match the entire block, so regular expressions no longer nee…
470 Postprocessors munge the document after the ElementTree has been serialized into a string. Postproc…
564 serialized, a postprocessor will replace the placeholder with the raw string. This prevents subsequ…
783 imported, a user can include it with the above syntax.
822 registry = Registry()
825 item = registry[0]
827 item = registry['itemname']
837 assert 'itemname' in registry
839 assert someitem in registry
[all …]
|