explanation behind that says it's just coercion of one type plus another.
What is happening there is actually a code block and a unary + which coerces the array into 0.
({} + []) would get the same as ([] + {}) understandably.

The callable constructor proposal was withdrawn because "the same problems can be solved with decorators" but the readme here doesn't show examples of that. Can you please update that for reference? It would be really helpful.

If this is something currently supported, let me know and I can make it more clear in the docs.

The "run" options in a scheme have several options that are unable to be set via XcodeGen. Namely those in the "Options" and "Diagnostics" tabs:

![2018-06-28 at 2 07 pm](h

Documentation does not specify clearly what the expression field stands for.
I believe (looking at implementations) that it is to make the difference between block body and expression body.
However this information seems redundant with the nature of the field body itself. So I imagine it is to respect the context less clause, but the latter refers only to parent node and not to childre

I am looking to enforce documentation on the interfaces and all of its properties using eslint. I have installed eslint-plugin-tsdoc package in my project. Is there a rule to enforce it?

Thanks

It looks like conventional commits do not explicitly specify whether a description should begin with an uppercase or lowercase letter, although all the examples appear to begin with a lowercase letter.

Could the next revision recommend that the description starts with a lowercase letter? Something like:

A description SHOULD begin with a lowercase letter, except when the first word would no

The Kafka spec states that the JSON format MUST be used for Kafka versions that do not support headers

Following #463, I'd simply say that any structured format that adheres to compatibility with the original JSON MUST be used. And that JSON COULD be used for human readability...

Lemme know your thoughts 😷

The spec defines a single core trait ManualScaler, but seems to be missing additional core traits that are implemented by Rudr:
https://github.com/oam-dev/spec/blob/master/5.traits.md#core-traits

Rudr implements the following additional traits that are not defined in the spec:

• ingress.core.oam.dev/v1alpha1
• auto-scaler.core.oam.dev/v1alpha1
• volume-mounter.core.oam.dev/v1alpha1

@chris-little's feedback from CesiumGS/3d-tiles#405:

Can tilesets be nested hierarchically? I'm not sure from the text.
Can a tile can be "in" more than one tileset? I'm not sure how, but presumbly URIs allow this.

The answers are "yes" and "yes" but they could be clarified in the reference card.

It would be useful to have some short documents that we can point people to (and link in the README) about how to file effective feature requests (e.g. that problem statements are more useful than feature requests, at least in isolation). It also might be useful to provide some guidance to users on best practices for interacting with the issue tracker.

cc @natebosch

A few nights ago I wanted to show someone how cool specs2 was. There was no computer nearby so I used my phone. Unfortunately the examples on the website kept scrolling out of the screen and are not given sufficient screen space for proper viewing. Numerous additional line breaks are introduced because the code area only uses maybe 50% to 70% of the screen's width.
This did not exactly help selli

The gitbook CLI tool has been deprecated. Let's find an alternative, e.g. mdbook.

Currently the empty of Monoid is specified as a nullary function rather than a plain value. Is there a plausible use case that benefits from empty being a function or requires it to be a function?

At the moment, I'm tempted to specify empty as a plain value in [a use case of monoid](https://github.com/calmm-js/p

The README of the 2.0.0 examples hasn't been updated with the release: https://github.com/asyncapi/asyncapi/blob/master/examples/2.0.0/README.md. We should update accordingly or remove it.

CIR-2017-255

During oCIG call 5 the issue of potential future conflicts in function names was raised. In particular, the following scenario was expressed as an example:

• A vendor X adds a vendor-specific function foo()
• The oCIG decides that foo() is generally useful and adopts it as a standard function
• The oCIG disagrees with (a detail of) th

When filtering by sender or receiver, the stats selection algorithm is as follows:

- If selector is an RTCRtpSender, gather stats for and add the following objects to result:
  * All RTCOutboundRTPStreamStats objects representing RTP streams being sent by selector.
  * All stats objects referenced directly or indirectly by the RTCOutboundRTPStreamStats objects added.
- If selector is an

Update the rendering makes paint timing for each document right before updating the rendering (painting) in step 13 and computes rendering end time for reporting long tasks in step 12. Because this sandwitches the painting operation, it can be used to measure the paint time with a high precision.

• This is a request to minor update documentation
• where the error appears: http://www.openmobilealliance.org/wp/OMNA/LwM2M/LwM2MRegistry.html#omalabel
• Item in error is documentation of urn:oma:lwm2m:oma:6
• Detail: I believe that the Description string should appropriately say this object is for the location related information of the device such as its lat/long position and velocity.

In VDOM Event Support there are two lines with typos in the first code example; corrected:

from IPython.display import display

return button(str(count), onClick=on_click, style={'width': '100', 'height': '40'})

The second code example has typos, too, corrected:

from IPython.display import display

model

Please Indicate One:

• [X ] Editorial
• Question
• Feedback
• Blocking Issue
• Non-Blocking Issue

Please Describe the Issue:

Section https://www.w3.org/TR/activitystreams-core/#compact-uris talks about using JSON-LD syntax involving "id" but https://www.w3.org/TR/json-ld/#compact-iris only talks about "@id", nowhere is "id" mentioned.

I'm pretty sure that there are TileJSON files - as well as services and data - around which contain maskLevel.
The logic is described here: https://github.com/mapbox/tilelive-vector
Should'nt this be part of the spec.?

@Valodim wanted to open an issue about writing a paragraph wrt "why not encrypt by default" into the FAQ. The question seems to come up quite often.

This issue is here to remind him of opening it.

The Overview and FullModel modelNames are used to identify the correct sub layers in client applications like SceneViewer, but are not documented here: https://github.com/Esri/i3s-spec/blob/master/docs/1.7/subLayerModelName.md

To name "Proofmarshal" is not good if we have not a reference added as a footnote. Also it could be nice to add some notes on "single-use-seal" and “Proof-of-Publication-Ledgers”. I know only the blog post https://petertodd.org/2016/commitments-and-single-use-seals on the topic.