The workaround sucked so hard -> use traditional for!