Migration from hfg to hog

The repository still uses hfg at an older commit point. This issue is to discuss the move from hfg to hog, if anything needs to be looked after during migration.

assigned to @pponkumar

@he66coqe fyi

marked this issue as related to hog#25 (closed)

I thought of initiating the switch from hfg to hog, the modifications in generate.py is straight forward I guess. But the issue I see is that we need to generate all the operators again and then the diffs and history gets complicated.

Is this okay? Or is there a way to do this better that would make sense?

Thanks for taking this on and feel free to go ahead! I think the purpose of this extra repo is that we will "pollute" the history here, but not in the hyteg repo - so it "avoids" the problem you mentioned :) maybe @he66coqe has some additional input, though.

I second that. We do not care about history here :).

Additionally, I'd like to mention #3 (closed). I had the idea that we let the CI regenerate the operators to reduce manual labor. If you want, you can also have a stab at that or ask me to prioritize it ^^.

Great then, I will go ahead with the switch.

Honestly, #3 (closed) looks interesting but may not be possible now, maybe a fun thing to stab in the summer break if it be still open!

mentioned in merge request !8 (merged)

Closing this in favour of !8 (merged)

closed