Update several references to v0.10 or latest docs.rs (#67)

Author: Lambdanaut

src/faq/code.md

@@ -205,7 +205,7 @@ impl StaticUtil {
 }
 ```
 
-[`Aether`](https://docs.rs/gdnative/0.9/gdnative/prelude/struct.Aether.html) is a special user-data wrapper intended for zero-sized types, that does not perform any allocation or synchronization at runtime.
+[`Aether`](https://docs.rs/gdnative/latest/gdnative/export/user_data/struct.Aether.html) is a special user-data wrapper intended for zero-sized types, that does not perform any allocation or synchronization at runtime.
 
 The type needs to be instantiated somewhere on GDScript level.
 Good places for instantiation are for instance:
@@ -456,4 +456,4 @@ If you require insight into Rust code that is not exported to Godot or would lik
 
 **Note:** There are many more profilers than the ones listed and you should do your own research before selecting which one you wish to use.
 
-For more information about profiling and other rust performance tips, please check out the [Rust performance book](https://nnethercote.github.io/perf-book/profiling.html).
+For more information about profiling and other rust performance tips, please check out the [Rust performance book](https://nnethercote.github.io/perf-book/profiling.html).

src/gdnative-overview/data-representations.md

@@ -42,7 +42,7 @@ _See `GodotObject`, the Rust trait implemented for all Godot classes, in [godot-
 
 Since GDScript is a dynamic language, you often deal with variants implicitly. Variables which are not type-annotated can have values of multiple types throughout their lifetime. In static languages like Rust, every value must have a defined type, thus untyped values in GDScript correspond to `Variant` in Rust. Godot APIs which accept any type as parameter are declared as `Variant` in the GDNative bindings (and thus godot-rust library). Sometimes, godot-rust also provides transparent mapping from/to concrete types behind the scenes.
 
-Variants also have a second role as a serialization format between Godot and Rust. It is possible to extend this beyond the built-in Godot types. To make your own types convertible from and to variants, implement the traits [`FromVariant`](https://docs.rs/gdnative/latest/gdnative/core_types/trait.FromVariant.html) and [`ToVariant`](https://docs.rs/gdnative/latest/gdnative/core_types/trait.ToVariant.html). Types that can only be safely converted to variants by giving up ownership can use [OwnedToVariant](https://docs.rs/gdnative/0.9.3/gdnative/core_types/trait.OwnedToVariant.html), which is similar to the Rust `Into` trait.
+Variants also have a second role as a serialization format between Godot and Rust. It is possible to extend this beyond the built-in Godot types. To make your own types convertible from and to variants, implement the traits [`FromVariant`](https://docs.rs/gdnative/latest/gdnative/core_types/trait.FromVariant.html) and [`ToVariant`](https://docs.rs/gdnative/latest/gdnative/core_types/trait.ToVariant.html). Types that can only be safely converted to variants by giving up ownership can use [OwnedToVariant](https://docs.rs/gdnative/latest/gdnative/core_types/trait.OwnedToVariant.html), which is similar to the Rust `Into` trait.
 
 _See `Variant` in
 [godot-rust docs](https://docs.rs/gdnative/latest/gdnative/core_types/struct.Variant.html),

src/getting-started.md

@@ -6,4 +6,4 @@ This tutorial assumes some experience with Godot's GUI and GDScript. It assumes
 
 ## Work-in-progress
 
-**The Getting Started tutorial is a work-in-progress, and currently it only covers up to the hello-world example!** To learn more about the API after the tutorial, you'll have to dive into the [documentation on docs.rs](https://docs.rs/gdnative/0.9), and the [other examples in the main repo]( https://github.com/godot-rust/godot-rust/tree/master/examples/). If you have any questions using the bindings, ask away in the `#gdnative_dev` channel on the [Godot Engine community Discord server](https://godotengine.org/community)!
+**The Getting Started tutorial is a work-in-progress, and currently it only covers up to the hello-world example!** To learn more about the API after the tutorial, you'll have to dive into the [documentation on docs.rs](https://docs.rs/gdnative/latest), and the [other examples in the main repo](https://github.com/godot-rust/godot-rust/tree/master/examples/). If you have any questions using the bindings, ask away in the `#gdnative_dev` channel on the [Godot Engine community Discord server](https://godotengine.org/community)!

src/getting-started/hello-world.md

@@ -36,7 +36,7 @@ Once the project is created, open `Cargo.toml`, change the crate type to `cdylib
 crate-type = ["cdylib"]
 
 [dependencies]
-gdnative = "0.9"
+gdnative = "0.10"
 ```
 
 > ### Organization of Rust code
@@ -187,4 +187,4 @@ You can find the full code for this example in the main repo: [https://github.co
 
 ## Work-in-progress
 
-**The Getting Started tutorial is a work-in-progress, and unfortunately it ends here for now!** To learn more about the API, you'll have to dive into the [documentation on docs.rs](https://docs.rs/gdnative/0.9), and the [other examples in the main repo]( https://github.com/godot-rust/godot-rust/tree/master/examples/). If you have any questions using the bindings, ask away in the `#gdnative_dev` channel on the [Godot Engine community Discord server](https://godotengine.org/community)!
+**The Getting Started tutorial is a work-in-progress, and unfortunately it ends here for now!** To learn more about the API, you'll have to dive into the [documentation on docs.rs](https://docs.rs/gdnative/latest), and the [other examples in the main repo]( https://github.com/godot-rust/godot-rust/tree/master/examples/). If you have any questions using the bindings, ask away in the `#gdnative_dev` channel on the [Godot Engine community Discord server](https://godotengine.org/community)!

src/rust-binding/properties.md

@@ -93,7 +93,7 @@ For cases not covered by the `#[property]` attribute, it may be necessary to man
 
 This is often the case where custom hint behavior is desired for primitive types, such as an Integer value including an `IntEnum` hint.
 
-To do so, you can use the [`ClassBuilder`](https://docs.rs/gdnative/0.9.3/gdnative/prelude/struct.ClassBuilder.html) -- such as in the following examples -- to manually register each property and customize how they interface in the editor.
+To do so, you can use the [`ClassBuilder`](https://docs.rs/gdnative/latest/gdnative/prelude/struct.ClassBuilder.html) -- such as in the following examples -- to manually register each property and customize how they interface in the editor.
 
 ```rust
 #[derive(NativeClass)]
@@ -153,4 +153,4 @@ impl MyNode {
         self.number = new_value
     }
 }
-```
+```

src/rust-binding/to-variant-from-variant-export.md

@@ -31,7 +31,7 @@ For more information about how you can customize the behavior of the dervive mac
 
 ## Export Trait
 
-The Godot editor retrieves property information from [Object::get_property_list](https://docs.godotengine.org/en/stable/classes/class_object.html#id2). To populate this data, `godot-rust` requires that the [`Export`](https://docs.rs/gdnative/0.9.3/gdnative/nativescript/trait.Export.html) trait be implemented for each type Rust struct.
+The Godot editor retrieves property information from [Object::get_property_list](https://docs.godotengine.org/en/stable/classes/class_object.html#id2). To populate this data, `godot-rust` requires that the [`Export`](https://docs.rs/gdnative/latest/gdnative/nativescript/trait.Export.html) trait be implemented for each type Rust struct.
 
 There are no derive macros that can be used for `Export` but many of the primitive types have it implemented by default.
 
@@ -47,7 +47,7 @@ struct Foo {
 }
 
 impl Export for Foo {
-    // This type should normally be one of the types defined in [gdnative::nativescript::hint](https://docs.rs/gdnative/0.9.3/gdnative/nativescript/init/property/hint/index.html).
+    // This type should normally be one of the types defined in [gdnative::export::hint](https://docs.rs/gdnative/latest/gdnative/export/hint/index.html).
     // Or it can be any custom type for differentiating the hint types.
     // In this case it is unused, so it is left as ()
     type Hint = ();