[FEA]: Abstract build step in cccl.c.parallel

[gevtushenko]

Is this a duplicate?

• I confirmed there appear to be no duplicate issues for this request and that I agree to the Code of Conduct

Area

General CCCL

Is your feature request related to a problem? Please describe.

Porting algorithm to cccl.c.parallel involves a lot of boilerplate code in build step. Depending on if an iterator has a state or not, we have to generate a string with C++ wrappers. Same applies to operators. We were able to abstract this in cuda.cooperative, so it should be possible to abstract build step in cccl.c.parallel as well:

cccl/python/cuda_cooperative/cuda/cooperative/experimental/warp/_warp_merge_sort.py

Lines 46 to 61 in e149e86

	template = Algorithm('WarpMergeSort',
	'Sort',
	'warp_merge_sort',
	['cub/warp/warp_merge_sort.cuh'],
	[TemplateParameter('KeyT'),
	TemplateParameter('ITEMS_PER_THREAD'),
	TemplateParameter('VIRTUAL_WARP_THREADS')],
	[[Pointer(numba.uint8),
	DependentArray(Dependency('KeyT'),
	Dependency('ITEMS_PER_THREAD')),
	DependentOperator(Constant(numba.int8), [Dependency('KeyT'), Dependency('KeyT')], Dependency('Op'))]],
	type_definitions=[numba_type_to_wrapper(dtype, methods=methods)])
	specialization = template.specialize({'KeyT': dtype,
	'VIRTUAL_WARP_THREADS': threads_in_warp,
	'ITEMS_PER_THREAD': items_per_thread,
	'Op': compare_op})

Describe the solution you'd like

We should try abstracting build step for cccl.c.parallel algorithms. If we recognize that certain kernel parameters are iterators / operators, we could automate generating C++ wrappers.

Describe alternatives you've considered

No response

Additional context

No response

[jollylili]

@wmaxey, I'd like to check in to see if this item is on track? We have 10/10, and 11/14 as estimated start and end date respectively.