Add JSpecify 0.3 annotations, and a "fake" @NullnessUnspecified annotation

2022-12-12 18:53:22 -08:00
parent e3282d090d
commit 2329ee5f84
11 changed files with 977 additions and 1 deletions
@@ -0,0 +1,39 @@
+/*
+ * Copyright 2018-2020 The JSpecify Authors.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.jspecify.annotations;
+
+import static java.lang.annotation.ElementType.TYPE_USE;
+import static java.lang.annotation.RetentionPolicy.RUNTIME;
+
+import java.lang.annotation.Documented;
+import java.lang.annotation.Retention;
+import java.lang.annotation.Target;
+
+/*
+
+
+        This is a fake annotation that does not exist in the JSpecify 
+        release, and with no expectation of being added!
+
+        Once Kotlin supports @NullUnmarked, the tests can be updated
+        and this should be removed.
+
+
+ */
+@Documented
+@Target(TYPE_USE)
+@Retention(RUNTIME)
+public @interface NullnessUnspecified {}