Hide call to unsafe method inside of an unsafe block in rooting macro.

[jdm]

This usage of initial() is safe because we're storing the result directly inside of a rooted location.

[sagudev]

this could cause warnings for rooted! inside unsafe blocks (due to unsafe inside unsafe). see rust-lang/rust#74838

[jdm]

this could cause warnings for rooted! inside unsafe blocks (due to unsafe inside unsafe). see rust-lang/rust#74838

We can allow that when it happens. It's better than requiring unsafe blocks in code that does not require them, which is a problem I hit when trying to use this version of the macro.

[sagudev]

this could cause warnings for rooted! inside unsafe blocks (due to unsafe inside unsafe). see rust-lang/rust#74838

We can allow that when it happens. It's better than requiring unsafe blocks in code that does not require them, which is a problem I hit when trying to use this version of the macro.

I have a feeling this happens a lot in servo (if before unsafe was required). So we could simply put #[allow(unused_unsafe)] in macro: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=80541d5b4fbe5645e4f9e47d4d496d1b

[jdm]

The isn't a version of the macro that we use very often in Servo right now. I did not need to modify any existing code with these changes.