Thanks for taking the time to ask on Meta!

I remember handling that flag. I didn't find the question particularly stellar, but I did notice this:

Is there a better way to add up all 16 uint16s and store the result in an int?

The rest of the question went well above my head, but if it all boiled down to finding a better way to [insert what the code currently does here], then that's probably what motivated the migration from Programmers.SE; after all, that's what we do here: we take your working code, and make it better - for quite a number of values of better.

According to the revision history of the question in question, it was single-handedly migrated here by World Engineer♦.

The post isn't blatantly off-topic on Code Review; I don't blame World Engineer for bringing it on our turf. Would it be better off on Stack Overflow? Perhaps. But if the question isn't off-topic on Code Review, then it should stay on Code Review. Especially if it was migrated from another site, regardless of whether it was migrated by community votes or a moderator: nobody likes being bounced from one SE site to the next.

So I had to decide, and I declined your flag with that specific canned reason, because as you later found out, there's already a migration path set up to Stack Overflow:

• Flag > Should be closed... / 3K+ rep simply Vote to Close
• Off-Topic
• Question belongs on another site in the Stack Exchange network
• Pick a migration target
• Sit & wait

The last step is where the community gets involved: by flagging off-topic, you make the post enter the review queues, and the community votes to either leave the question opened, or agree with your flag and cast a vote to close/migrate, and with enough votes in favor, the question gets migrated.

Because there's an existing migration path for the target site, at no point in time a moderator needs to step in for this to happen: that's why I declined your flag.

Custom-flagging for migration should be for migrating to sites without an existing migration path - like for migrating from Stack Overflow to here.

Thanks for taking the time to ask on Meta!

I remember handling that flag. I didn't find the question particularly stellar, but I did notice this:

Is there a better way to add up all 16 uint16s and store the result in an int?

The rest of the question went well above my head, but if it all boiled down to finding a better way to [insert what the code currently does here], then that's probably what motivated the migration from Programmers.SE; after all, that's what we do here: we take your working code, and make it better - for quite a number of values of better.

According to the revision history of the question in question, it was single-handedly migrated here by World Engineer♦.

The post isn't blatantly off-topic on Code Review; I don't blame World Engineer for bringing it on our turf. Would it be better off on Stack Overflow? Perhaps. But if the question isn't off-topic on Code Review, then it should stay on Code Review. Especially if it was migrated from another site, regardless of whether it was migrated by community votes or a moderator: nobody likes being bounced from one SE site to the next.

So I had to decide, and I declined your flag with that specific canned reason, because as you later found out, there's already a migration path set up to Stack Overflow:

• Flag > Should be closed... / 3K+ rep simply Vote to Close
• Off-Topic
• Question belongs on another site in the Stack Exchange network
• Pick a migration target
• Sit & wait

The last step is where the community gets involved: by flagging off-topic, you make the post enter the review queues, and the community votes to either leave the question opened, or agree with your flag and cast a vote to close/migrate, and with enough votes in favor, the question gets migrated.

Because there's an existing migration path for the target site, at no point in time a moderator needs to step in for this to happen: that's why I declined your flag.

Custom-flagging for migration should be for migrating to sites without an existing migration path - like for migrating from Stack Overflow to here.

Thanks for taking the time to ask on Meta!

I remember handling that flag. I din't find the question particularly stellar, but I did notice this:

Is there a better way to add up all 16 uint16s and store the result in an int?

The rest of the question went well above my head, but if it all boiled down to finding a better way to [insert what the code currently does here], then that's probably what motivated the migration from Programmers.SE; after all, that's what we do here: we take your working code, and make it better - for quite a number of values of better.

According to the revision history of the question in question, it was single-handedly migrated here by World Engineer♦.

The post isn't blatantly off-topic on Code Review; I don't blame World Engineer for bringing it on our turf. Would it be better off on Stack Overflow? Perhaps. But if the question isn't off-topic on Code Review, then it should stay on Code Review. Especially if it was migrated from another site, regardless of whether it was migrated by community votes or a moderator: nobody likes being bounced from one SE site to the next.

So I had to decide, and I declined your flag with that specific canned reason, because as you later found out, there's already a migration path set up to Stack Overflow:

• Flag > Should be closed... / 3K+ rep simply Vote to Close
• Off-Topic
• Question belongs on another site in the Stack Exchange network
• Pick a migration target
• Sit & wait

The last step is where the community gets involved: by flagging off-topic, you make the post enter the review queues, and the community votes to either leave the question opened, or agree with your flag and cast a vote to close/migrate, and with enough votes in favor, the question gets migrated.

Because there's an existing migration path for the target site, at no point in time a moderator needs to step in for this to happen: that's why I declined your flag.

Custom-flagging for migration should be for migrating to sites without an existing migration path - like for migrating from Stack Overflow to here.

Thanks for taking the time to ask on Meta!

I remember handling that flag. I didn't find the question particularly stellar, but I did notice this:

Is there a better way to add up all 16 uint16s and store the result in an int?

The rest of the question went well above my head, but if it all boiled down to finding a better way to [insert what the code currently does here], then that's probably what motivated the migration from Programmers.SE; after all, that's what we do here: we take your working code, and make it better - for quite a number of values of better.

According to the revision history of the question in question, it was single-handedly migrated here by World Engineer♦.

The post isn't blatantly off-topic on Code Review; I don't blame World Engineer for bringing it on our turf. Would it be better off on Stack Overflow? Perhaps. But if the question isn't off-topic on Code Review, then it should stay on Code Review. Especially if it was migrated from another site, regardless of whether it was migrated by community votes or a moderator: nobody likes being bounced from one SE site to the next.

So I had to decide, and I declined your flag with that specific canned reason, because as you later found out, there's already a migration path set up to Stack Overflow:

• Flag > Should be closed... / 3K+ rep simply Vote to Close
• Off-Topic
• Question belongs on another site in the Stack Exchange network
• Pick a migration target
• Sit & wait

The last step is where the community gets involved: by flagging off-topic, you make the post enter the review queues, and the community votes to either leave the question opened, or agree with your flag and cast a vote to close/migrate, and with enough votes in favor, the question gets migrated.

Because there's an existing migration path for the target site, at no point in time a moderator needs to step in for this to happen: that's why I declined your flag.

Custom-flagging for migration should be for migrating to sites without an existing migration path - like for migrating from Stack Overflow to here.