-
I believe that we should adopt clear guidelines about what kind of stuff we want to have support for.
Clearly we need first class support for literals, especially list of strings, since IMO it's the …
-
Create a proper contribution guidelines document.
-
# Suggestion
I have a factory function that takes a specification in the form of an object literal and returns a class. If the description passed in is a literal and annotated with `as const`, then…
-
Hi there, thanks for sharing your QA resource!
https://github.com/deepset-ai/COVID-QA/tree/master/data/question-answering
I was wondering if you have a write-up of the annotation methodology? For …
-
HDT contains a large number of trees that my scripts have identified as having a greater degree of non-projectivity than is typical in UD. After reviewing the data, I have some questions about how thi…
-
Lessons learned from recent experiences
-
CRI-O is not following Kubernetes conventions for annotations. See https://kubernetes.io/docs/reference/labels-annotations-taints/ for what actual Kubernetes annotations look like. This means we could…
-
Hi!
I notice that you write the return statement in some test cases. For example,
Generally, the purpose of a test case is to determine if different features within a system are performing as …
-
The first exmplum in Source/Specs/standOff.xml contains
~~~xml
This example … used by ISO 24611 (MAF).
~~~
But there is no element with an `@xml:id` of `"ISO24611"` in P5.
Turns out our re…
-
The following sentence appears to be a case of clause coordination with an elided verb in the latter two clauses, but the analysis doesn't seem to match with what I can find in the [UD guidelines](htt…