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.

I've received a lot of feedback from devs while working on getting Mithril, Lodash and Rx to support Fantasy Land regarding the heady language used in the specification. It is intimidating and creates the impression that it won't be helpful in their work.

I personally think using precise language in a specification is exactly the right thing to do. But I do think it would be beneficial to expla

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

The spec in https://github.com/estree/estree/blob/master/es2020.md states

bigint property is the string representation of the BigInt value. It doesn't include the suffix n.

Should this represent the source text or a normalized notation?

In other words; is the AST for 1048575n equivalent to that of 0xfffffn or not due to the .bigint field?

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

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.

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

@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.

Ref: https://github.com/WebAssembly/design/blob/master/Nondeterminism.md

Should clearly explain how do we handle these cases.

In short: Out of that list only two things affect ewasm:

• NaN on arithmetic operations. This only affects floating point, which we reject at deploy time.
• Resource exhaustion (such as out of memory, etc.). This is handled via the metering process.

Also see #90

In fuent.js, we restricted the options to NUMBER and DATETIME beyond what's documented in the guide right now.

We should port those changes over.

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

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

Introduction

This is a proposal for adding more explicit and extensive, and even ASCII art inspired support for set algebra in openCypher.

In my opinion sets of graphs is a once-in-a-lifetime opportunity that is much more than a revival: Doing set algebra on sets of graphs is potentially several orders of magnitude more powerful than SQL-based set algebra (or the simple lists etc. offered

What is the problem you're trying to solve
Kubernetes is a major target for compose specification, so we should establish canonical mapping for compose elements

Describe the solution you'd like
Can leverage https://github.com/kubernetes/kompose/blob/master/docs/conversion.md

• define custom fields when relevant

Additional context
Also see https://github.com/docker/compose-on-

Need to have a section in the security considerations section to say that we need to be careful to not leak information about whether TCP ports are open or closed.

The Privacy & Security section refers readers to an external document for actual details on possible mitigations.
Mitigations should outlined directly in the spec, so we need to move over the relevant parts from that document into the spec.

• 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.

Some tile server implementations support overzooming, where tiles are generated and served at zoom levels beyond a tileset's zoom extent using the lowest available zoom level as the source of truth for overzoomed tiles.

Mapbox's tile server includes an overzoom max of 30 for all vector tilesets, which means tiles can be requested from any tilese

@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.