Swapping the order of field declarations lead to an unexpected results.

[Tsuku-Yomi]

When script

using System.Collections;
using System.Collections.Generic;
using Unity.Mathematics;
using UnityEngine;

public class Test : MonoBehaviour
{
    int i1;
    float i2;

    void Start()
    {
        i1 = 1;
        i2 = 1.5f;
    }

    void Update()
    {
        Debug.Log(i1);
    }
}

swap the declaration positions of i1 and i2 and reload to

using System.Collections;
using System.Collections.Generic;
using Unity.Mathematics;
using UnityEngine;

public class Test : MonoBehaviour
{
    float i2;
    int i1;

    void Start()
    {
        i1 = 1;
        i2 = 1.5f;
    }

    void Update()
    {
        Debug.Log(i1);
    }
}

expected output was 1, but the actual output was 1069547520 (this is the value of a 1.5 as an integer in binary).

[handzlikchris]

Hmm - that's interesting. I think somewhat expected as well. What happens is you get another class after reload that's Test__Patched_ and in your old instance theres a IL jump statement that moves code execution to your new class but it doesn't change what's on IL stack at all.

That's why when you add new fields - there's a 'hack' that gets it to work. This this one falls under same limitation.

Ideally when you change class by adding / changing fields you'd do a full recompile to avoid surprises and then iterate further in method bodies.