How can improper use of unawaited Futures introduce subtle bugs, such as a race condition or an unhandled error, into a Flutter application, and how does the unawaited function help make this deliberate choice explicit?

Calling a function that returns a Future without actually awaiting it means your code immediately continues executing without ever actually waiting for that specific asynchronous operation to complete, which can introduce a genuine race condition if your subsequent code incorrectly assumes that operation has already finished, or result in a completely unhandled error being silently and invisibly swallowed if that Future eventually fails, and wrapping a genuinely intentional fire and forget call with Dart's unawaited function makes this deliberate choice explicit and clearly visible to anyone reading the code, distinguishing it from an accidentally forgotten await that a linter might otherwise flag as a likely genuine mistake.

import 'dart:async';

void logAnalyticsEvent(String eventName) {
  unawaited(analyticsService.logEvent(eventName));
}