Bug 1524822 - Fix warnings with rust 1.34+. r=jrmuizel

There's some new limited const fn support in stable, and this is the recommended way to initialize atomics now. If this for some reason doesn't compile in all platforms / versions we support I'll just sprinkle some #[allow(deprecated)] instead. Also, cargo changes the output of Cargo.lock, see rust-lang/cargo#6180. So also update those comments. Differential Revision: https://phabricator.services.mozilla.com/D18495 UltraBlame original commit: 5f006a3c652c3a5def8800b9b0e65c4213b86785
marco-c · Oct 3, 2019 · 0f862e9 · 0f862e9
1 parent e795b3c
commit 0f862e9
Show file tree

Hide file tree

Showing 4 changed files with 50 additions and 4 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/gfx/wr/Cargo.lock b/gfx/wr/Cargo.lock
diff --git a/gfx/wr/webrender/src/device/gl.rs b/gfx/wr/webrender/src/device/gl.rs
@@ -275,7 +275,6 @@ atomic
 :
 {
 AtomicUsize
-ATOMIC_USIZE_INIT
 Ordering
 }
 ;
@@ -458,7 +457,13 @@ GPU_BYTES_ALLOCATED
 :
 AtomicUsize
 =
-ATOMIC_USIZE_INIT
+AtomicUsize
+:
+:
+new
+(
+0
+)
 ;
 /
 /

diff --git a/gfx/wr/webrender/src/picture.rs b/gfx/wr/webrender/src/picture.rs
@@ -373,7 +373,6 @@ atomic
 :
 {
 AtomicUsize
-ATOMIC_USIZE_INIT
 Ordering
 }
 ;
@@ -958,7 +957,13 @@ NEXT_TILE_ID
 :
 AtomicUsize
 =
-ATOMIC_USIZE_INIT
+AtomicUsize
+:
+:
+new
+(
+0
+)
 ;
 fn
 clamp