6502/CLK
1
0
Fork 0
mirror of https://github.com/TomHarte/CLK.git synced 2025-02-27 15:29:34 +00:00
Code Issues Projects Releases Wiki Activity

Added a further ambiguity.

Browse Source
This commit is contained in:
Thomas Harte 2022-04-29 05:08:44 -04:00
parent 824d3ae3f7
commit abd2a831a3
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
InstructionSets/M68k/Implementation/PerformImplementation.hpp
View File

@ -48,6 +48,11 @@ namespace M68k {
// 68ks the loads and stores could be performed immediately, for the accurate they could // 68ks the loads and stores could be performed immediately, for the accurate they could
// be enqueued, then performed, then a second call to perform that now has the data loaded // be enqueued, then performed, then a second call to perform that now has the data loaded
// could be performed. // could be performed.
//
// (5) is it really helpful for operation to be a template parameter? I'm trying to avoid forcing
// an additional `switch` if it's likely that the caller has already applied one, but does
// that objective justify the syntax overhead for callers that don't inherently have their
// own `switch`? Do the first sort of callers really exist?
template < template <
Operation operation, Operation operation,