Implement a function that returns 1 when a long value can be stored in an int without changing, and 0 when that conversion would lose information.

• value arrives as a long. Decide whether that exact number can live in an int, then return 1 or 0.
• On the grading runner an int covers -2147483648 to 2147483647, while a long covers a far wider range. So a long can hold numbers that no int can represent.
• Both ends of the range fit. -2147483648 and 2147483647 return 1, one step past either of them returns 0.
• Two techniques are accepted. Compare value against INT_MIN and INT_MAX from <limits.h>, or convert down and back with (long)(int)value == value and check whether the number came home unchanged.
• The round trip is safe to run here: converting an out of range long down to int keeps the low 32 bits on this toolchain rather than crashing, and that is what makes the loss visible.
• A truncated value can look perfectly reasonable. 4294967338 becomes 42 on the way down, and the answer is still 0.
• Return 1 or 0 and print nothing. The tests print the return value with %d followed by a newline.

Implement a function that returns 1 when a long value can be stored in an int without changing, and 0 when that conversion would lose information.

• value arrives as a long. Decide whether that exact number can live in an int, then return 1 or 0.
• On the grading runner an int covers -2147483648 to 2147483647, while a long covers a far wider range. So a long can hold numbers that no int can represent.
• Both ends of the range fit. -2147483648 and 2147483647 return 1, one step past either of them returns 0.
• Two techniques are accepted. Compare value against INT_MIN and INT_MAX from <limits.h>, or convert down and back with (long)(int)value == value and check whether the number came home unchanged.
• The round trip is safe to run here: converting an out of range long down to int keeps the low 32 bits on this toolchain rather than crashing, and that is what makes the loss visible.
• A truncated value can look perfectly reasonable. 4294967338 becomes 42 on the way down, and the answer is still 0.
• Return 1 or 0 and print nothing. The tests print the return value with %d followed by a newline.